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.
> TL;DR Getting end-users' and sponsors' feedback is crucial if you really want to build (/enhance) a good product, but it doesn't mean that you can let them "think with solutions" and mindlessly introduce suggested changes yourself. Business insights ought to be reforged...
> TL;DR Being a Software Architect is not a Super Senior Developer role, in fact its both leadership & management (these two are not the same) role that should act in parallel (& independently!) to other management dimensions (e.g. product, engineering or project). Based on my personal experience,...
> TL;DR Practical usage of database technologies has drifted quite far from academical theory we've (or at least I've) been taught at universities. In my case some lessons learned were pretty much contrary to opposite to what I've believes was correct as a...
> TL;DR Concepts of fragility & antifragility apply to software engineering as well - but contrary to the common belief, fragility of the system is not related to the number of bugs or resilience (e.g. MTTR). It's far more about dichotomies between high inertia & high...
> TL;DR Subscription-based distribution models tend to get more & more popular, but not for books, at least not yet. Many have an ambition of becoming "the Netflix of books" (see recent O'Reilly's announcement), but frankly - I don't like the...
> TL;DR Software systems, like all other kinds of systems, should be evaluated not only in terms of fitting their purpose & technical excellence. No system exists in a void, they are affected by time, local & global conditions, market fluctuations (not only in market related to system'...
