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 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...
> TL;DR Judging software engineeer's potential is not easy. Skill is in fact of secondary importance, experience may be a subject of diminishing returns, passion can manifest in very different forms. Fortunately there's one, particular personal trait, the one I call an Ability To Execute...
> TL;DR Aspiring tech companies invest a lot of time & effort in the latest frameworks, most hyped platforms or hippie operating models, while in the same time their so-called knowledge management is taken straight from the 80s. It's the highest time (if you haven't...
