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 If you see that teams "reject" the (part of) codebase, working with it lowers their engagement level, they have neither energy nor will to tackle its challenges, it's very rarely the matter of codebase's size. Sober-minded engineers just do not want...
> TL;DR HR departments of IT companies have discovered software craftsmanship conferences & realized their recruitment potential - this has turn the money tap on, but the pressure to make the conferences more approachable for any developer (that's what recruiters expect) results in quantity slowly taking over...
> TL;DR Many of the most commonly used patterns & "conceptual industry standards" in software development have their roots in Object-Oriented design. However, it's time to realize that OO is not the only viable way this day, so in some cases yesterday's anti-patterns...
> TL;DR Deploying 100 times per day is impressive, so is having 5k devs working in parallel on the same codebase, serving hundreds of thousands different API consumers around whole globe or handling fluently interest spike of several millions of new users due to world-scale news event. But there&...
> TL;DR Not all code (or rather - not code in any shape) can be tested in automated way. To assure its "proneness" to automation it has to be either written with certain qualities or refactored to provide them. There are only two ways to prevent these...
> TL;DR Effectiveness of professional training depends on several factors, including trainee's motivation, interest in the topic, its usefulness & relevance (now & in future), but also how rare (scarce) it is (training itself or the knowledge), how hard was it to obtain it, whether it was...
