In previous post I’ve explained briefly what actor model is and why it’s so fun. Today we’ll create our ActorSystem instance, learn what it is and send first messages to them. I hope it will be nice and easy start.
Rafał Hryniewski | użytkownik
Actor model concept fascinated me since I’ve heard about it for the first time. It’s been on my todo list ever since and Get Noticed 2017 is great opportunity to give it a try. That’s why there is an actor responsible for almost anything in Me2.0. But, what is an actor, actor model and are benefits of using it in our projects? You’ll find out in a minute.
Until recently I was into ASP.NET MVC because of it’s possibility to extending, modifying and doing pretty much whatever you want with it. And while I’ve got rather proficient in plugging stuff in it’s pipeline and/or doing custom stuff like routing, binding or results, it never changed one fact about MVC – it’s big, really big. And the truth is, some times we don’t want so much. That’s why I wanted to give Nancy a go for some time, below you’ll find some of my first thoughts. And i must tell you now, it...
I’m building my Get Noticed project from the scratch. And since 3 months is actually a very short span of time, I need compromise between doing some things fast (boring ones) and doing other things in a way that will allow me to write about it and not be ashamed to show some code afterwards. That means I’ll need to incur a technical debt in few areas of project. And I must watch it closely to not allow it to grow without control or interests will probably kill me.
Maile, smoki i tajemnice i HoloLens, czyli – Daj się poznać! Daj się poznać to już druga edycja konkursu organizowanego przez Maćka Aniserowicza. Tym razem nie może i mnie tam zabraknąć 🙂 W tym roku postanowiłem, iż muszę wystartować.
Jak doszedłem do tego co zawiniło i dlaczego OData na spatial queries mi nie działała. Czyli mały przewodnik po tym jak można debuggować zewnętrzny kod z poziomu Visual Studio. Coś co może nie na co dzień ale raz na jakiś czas może się bardzo przydać!
Since my project will be hosted on Azure App Services I want to ensure that every pushed commit will land in cloud environment and will be available outside of my local, dev machine. As close to it’s intended, production-like environment as possible. And with Azure App Services you can achieve basic continuous delivery without taking a sweat.
I’ve been working as software developers since July 2014 and during that time my point of view of IT industry have changed several times. Before starting my career I had absolutely no idea about this profession but even though I loved that! Why? Simply because of my friends who talked about tons of money they were earning, lots of benefits in the office including snacks, coffee, PlayStaion, alcohol and so on. That seemed awesome! Infamously, I must admit tha...
Exactly one year ago I’ve published first post on this blog. It was simple “Hello world” that were followed by some posts related to 2016 edition of Get Noticed contest and after that by some more or less technical related stuff. Since it’s first anniversary of this first, lame “Hello world” post I can’t just write simple “Hi there” again. And because I’m taking a little breath before 2017 edition of said contest I don’t want to write any hard, technical stuff. So let me tell you about some things that I...
This is one of those "I had to explain this couple times already so next time I want something I can redirect people to" kind of post. What I want to write about is difference in behavior between using new() and DbSet.Create() for instantiating new entities.
As you may already know I really, really like LINQ. One day I'll probably join together all my posts about this incredible featureand release pretty neat compendium/one-oh-one about this great feature. But while I'm not sitting and joining every post from this blog that have word "LINQ" in it into one, big pile, let's talk a bit about joining and grouping collections in LINQ.
Przy okazji konferencji PolCaster 2016 (na której byłem w zeszłym roku) usłyszałem dość interesującą informację, a mianowicie: statystycznie podcast kończy się po 7/8 odcinku. Później następuje wypalenie, lub brak pomysłów i bum…koniec. O ironio mój podcast również przez chwile mógł wydać się kolejnym kandydatem do zamknięcia, ale tak jak zapowiadałem w podsumowaniu roku… POWRÓCIŁ! Nie będę się tu zagłębiał i rozpisywał nad przyczynami tak sporej przerwy (bo trwa ona on września), ale z tego miejsca wszy...
Pracuję w strategii branch per feature. Co za tym idzie, na koniec każdego sprintu w lokalnym repozytorium mam sporo branchy, które stają się niepotrzebne. Wprowadza to niepożądany bałagan. Usuwanie każdego brancha z osobna to mozolna praca. Poniższa komenda pomaga mi usunąć niepotrzebne branche.
Pewnego razu trafiło mi się na facebookach takie pytanie „dlaczego z listy konwertuje na IEnumerable a odwrotnie nie” -cytat jest skopiowany żywcem, autor wolałby pozostać anonimowy. Jako że nie ma głupich pytań i każdy kiedyś zaczynał, odpowiem koledze i innym ciekawym. Ciekawi? No to lecim:)
So I've got two big, uppercase acronyms in title. Kind of double catchprase and if you're reading this, I've probably got your attention. And I hope to keep it so please, just don't stop reading, at least for a while. But why would you even consider stopping reading post about REST and some kind of API? Well, it's because I have lied and this post is not about this kind of REST that you've expected. Instead, it's about our human, common rest and recharging our batteries... and writing great REST APIs or ...
Nowadays, asynchronous programming isn’t something unusual. We all know that when it comes to do some I/O operations or HTTP request, we should do it async. Why? There’re several reasons but two most important are:Efficiency. In many cases, the code might work faster. That’s because it’s not forced to wait for the result. Instead, it can work on some other stuff and then come back for the response when it’s ready. Simple is that.Comfort. Async improves the comfort of using our applications. We don’t blo...
Aggregate is one of the most fun and powerful methods in LINQ. Sadly it's also of of the most underused and "scary" ones. I hope that after reading this post you will understand Aggregate a bit more, know when to use it and won't be afraid of doing so.
Some people can say 2016 was terrible year, for me it was one of the best, one of the most productive years as far as I remember. It was sort of game changer to me. So if you believe in balance in the universe, and last 12 month weren't so good for you, you must think there is a guy somehere, who stole your good fortune. Yup, it's me. I'm terribly sorry for that and ... I intend to make 2017 even better, at least for me ;).
macko (32 816,53)
http://pawlos.blo... (31 564,45)
pzielinski (27 178,29)
gordon_shumway (21 178,87)
paduda (20 336,33)
psz750 (13 018,14)
rroszczyk (10 383,88)
Damian (9 031,08)
danielplawgo (7 235,99)
arek (6 807,9)
burczu (6 214,22)
PaSkol (5 393,84)
lukaszgasior (4 097,38)
jj09 (3 498,06)
jedmac (3 298,38)
http://jakub-flor... (3 224,66)
CaMeL (2 954,87)
spetz (2 628,16)
mnikolajuk (2 596,93)
FutureProcessing (2 550,11)