> TL;DR Even today, many treat leading teams as a modern form of livestock herding. Limit the information (to avoid distraction), assign tasks, make a checkpoint each week, force controlled crunch before deadline, rinse & repeat. Fortunately, we can do so much better than that, if we manage to...
> 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...
Have you ever met a Bottleneck Superhero (BS)? I guess you can't tell as the term doesn't tell you anything. No surprise as I've just coined it for the sake of this blog post :> Yes, people who know me in person do know...
Once in a while I try to catch up on some classics I've somehow omitted to read. One of them is (was) Lencioni's "The Five Dysfunctions of a Team" [https://www.amazon.com/Five-Dysfunctions-Team-Leadership-Fable/dp/0787960756]. Title may cause setting some wrong expectations, subtitle...
I've recently read Lencioni's Five Dysfunctions of a Team [https://www.amazon.com/Five-Dysfunctions-Team-Leadership-Lencioni-ebook/dp/B006960LQW] - widely recognized classic on leadership & executive management. I'm not going for a full review here (you can easily find my review on Goodreads), but I want...
This blog post is some sort of a supplement to my previous post on building teams organically - you can find it here [https://no-kill-switch.ghost.io/growing-your-team-organically/]. As we all know, software developer job market is terribly twisted by huge disproportion between demand (crazy) & supply (barely dripping). Huge...
