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.
Experience makes you think you've gained an unquestionable license to generalizing :) At least that's what is happening regularly in my case. I tend to believe I see patterns I wasn't able to identify years ago. Maybe I'm right, or perhaps it'...
Life is so easy if you follow a method ("Gitflow"!). Or use a framework ( "Spring"!). Or implement a guideline ("Here's how you do functional programming on immutable data structures!"). The more specific, the better - it simplifies the judgment criteria whether you&...
It's one of the lessons I've learned the hard way: there's no other resource valuable more than your own time. Why so? * it's hard-capped * it's not transferable (my time isn't directly exchangeable with your time, at least in...
Doomsayers were claiming software developers would soon get replaced by Artificial Intelligence. Other "visionaries" predicted the inevitable rise of the generation of no-code/low-code tools that will make possible the development of various applications in natural language and/or in an entirely visual way - practically turning every...
Flat organizational structure - who wouldn't like that. But what does it really mean? Well, probably many teams who work in parallel - as independently as possible. Like separate micro-enterprises with clear ownership and well-defined product to look for. But does such a model work at scale? How...
I was fiddling a lot with a concept of Chaos Engineering [https://en.wikipedia.org/wiki/Chaos_engineering] (CE) recently. I find it VERY useful when it comes to building the resilience of platforms. But what if we could extend its applicability to other parts of our business/company? This...
