Developers can't fix bad management (2020)
I have a theory on why we&#x27;re seeing so much &quot;bad management&quot; for software engineers: most leaders at workplaces have not been engineers themselves at a company with a great engineering culture (I wrote about what I think this means [1]: it&#x27;s all the high-growth small and large tech companies we know)<p>The CEO, and the people under the CEO know and understand traditional, top-down management. Let the people with context and decision power make the big decisions, and pass this downwards. Works with finance, works with marketing, works with IT support, and should work with engineering as well... right?<p>But it actually doesn&#x27;t work with software engineers as well as it could. Or with designers. UX researchers. PMs... all these people would produce a magnitude more output when given proper context <i>and</i> autonomy.<p>A few leaders read about this, and try giving autonomy. These results end up even worse than the status quo, as you can&#x27;t just make it a free-for-all and expect it works overnight.<p>And to prove this point: look at companies where the founder <i>had</i> worked at a high-performing company before. Before founding Twilio, Jeff Lawson spent years at Amazon (he was one of the first AWS PMs), and in his book Ask Your Developer, he writes about just how much this experience shaped him, and all the practices he adopted from Amazon.<p>There&#x27;s this really weird divide between &quot;forward-looking tech companies&quot;[2] who &quot;get it&quot;, and everyone else. Which heavily benefits this first group.<p>[1] <a href="https:&#x2F;&#x2F;blog.pragmaticengineer.com&#x2F;the-developer-culture-test&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.pragmaticengineer.com&#x2F;the-developer-culture-tes...</a><p>[2] <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=25717390" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=25717390</a>