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 It's 2018 & for majority of developers speaking to a business person (/stakeholder /user /sponsor) is still a grand rarity. We explicitly ask for "layers" of intermediaries who can translate business to tech & back. And once it gets to crafting the actual...
> TL;DR No TL;DR today :) You either are interested in the recommendations or not really. I've promised not to make a typical year's summary, but I thought you guys may be interested in some book recommendations - frankly speaking I'm very happy with...
> TL;DR Some of the tech concepts that were slowly moving towards the mainstream in 2017 seem to introduce a fresh breathe into the way we create software. These concepts (one I call "Unconscious Computing" & Distributed Ledgers) aren't only about pure technology (how we...
> TL;DR Knowledge is power - you can't foresee & script creative way of knowledge workers if you really expect valuable outcomes. The only way is (once you get proper people first) to provide them necessary degree of freedom & contextual knowledge - up-to-date, comprehensible, applicable, broad...
> TL;DR Too many problems in modern software solutions development are related to chasm between 'thinkers' (analysts, people with business knowledge) & 'doers' (IT specialists, mainly programmers), yet we're so used to it we treat it as something carved in stone. Why not...
> TL;DR If maintainability & extensibility of your software are among the top priorities, readibility & easy-to-grasp correspondence to functional requirements are far more important than conciseness & technical "aesthetics" (e.g. compliance with patterns) of your code. That's why to build good...
