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 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'...
> TL;DR Vue.js is getting its high interest for a valid reason. Its 1st official conference has proven that it's backed up by the active & open community, its ecosystem is developing in interesting directions & in the end - there are valid (& safe) JS...
> TL;DR I keep seeing the term "Technical Debt" used as some sort of justification for bad engineering: "we had to pick our battles", "it will be fixed when it's time", "it's what happens to all apps with...
> TL;DR Solution that are both quick & easy to apply are usually a clear win, but in case of using cache to "fix" performance issues it may get really deceptive. Cache is a good tool (if applied correctly), but the concept of caching scales very poorly...
