Geek, agilista, blogger, codefella, serial reader. In the daylight - I navigate & lead software engineering. #lean #design #aws #elixir #analytics. I speak here for myself only.
There's an interesting trend of expanding the range of work products developers produce as the outcomes of their work. In software development prehistory it was just functional code (one that's supposed to provide business value directly). After some time automated tests have joined it - as...
Disclaimer: the idea of immutable code ain't mine - I've read/heard about it somewhere (can't recall precisely ;/) some time ago & it sticked with me. Code maintenance is already a huge problem & it won't get any better by itself. Software...
One of the things I'm truly & fully proud'n'happy is the way I'm managing my own self-development. I never had problems with: * declining motivation * making decisions on what to do next * lack of focus * burning out * losing ability to reach the state...
In 2016 pretty much every commercial software system built with modern tech is a distributed system. Yes, we all build distributed systems these days. Obviously, the term "distributed" is very spacious - I'm not saying we're all creating stuff like eventually consisted, sharded data...
It's a real grind, what we do here In real life, software delivery rarely is a piece of cake - writing actual, production code doesn't resemble "happy path" tutorials, industrial domain models are much more complex than "Animal -> Dog" hierarchy,...
Some time ago I had an interesting discussion with one of my colleagues regarding what is the typical thing that goes wrong when software delivery project turns out to be unsuccessful. Many of the reasons we've identified were not really revealing: * new, unknown, bleeding edge, unproven technology -...
