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 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...
> TL;DR Good engineering requires high awareness even in cases that may appear basic & straightforward. So-called good practice, if overdone or applied incorrectly can be very detrimental & in the same time may appear completely innocent & harmless, making us look for problems' root cause elsewhere. Using...
Disclaimer: even if this article is based mainly on my own experience & thoughts, this concept was very well formulated & articulated before I've managed to do it myself, in a blog post that you can find here. I advice you to read it first as I'...
> TL;DR Many IT (but not only) people run on adrenaline. We need action, we need bullets whistling around our heads, we need CHALLENGE! This addiction helps to achieve more, develop faster & wallow in satisfaction, but it can also be very dangerous as it makes us more prone...
