News for hackers. Stuff that matters.
Re:How Google Sold Its Engineers on Management by eldude on Monday April 20, 2015 @03:36PM (#9410342)
Survivorship bias. The history of Google's non-attempt to replace managers is almost comically bad. They announced in an all-hands meeting that going forward, all engineers would report directly to Larry Page and all project managers (present at the meeting) were out of a job. In other words, Google thought that managers were effectively useless, fired them publicly in front of the whole company, and didn't try to replace them with any manner of alternative.[1]

Long story short, it's not difficult to "sell" managers when the alternative is anarchy.

I think managers are toxic in an engineering organization, and a disincentive toward expertise; Rational intelligent engineers would be foolish not to abandon their expertise for a more rewarding (financially, politically, effort-wise) management track. That said, I consider it even more foolish to have nothing in their place. Managers serve a variety of roles that will be filled, implicitly or explicitly in any tribe/organization. Further, they resolve the matter of hierarchy and eliminate political position jockeying (while exacerbating other forms of politics).

If you pay attention, you'll see that modern software organizations are straining on the verge of breaking with current management styles. No viable alternative has reached mainstream (except maybe holocracy), but in the coming decade, one will.

In my company, we're replacing the classic management hierarchy with something closer to a federated republic where the various roles of management are broken into separate roles for separate individuals, with the goal of placing engineers on top with multiple peer-based support roles. Something close to this will be the software organizational hierarchy of the future.

[1] http://www.slate.com/blogs/business_insider/2014/04/25/googl...

Re:How Google Sold Its Engineers on Management by tkahnoski on Monday April 20, 2015 @04:09PM (#9410558)
I'd really love to chat or if you have some topics I can research. My current company is currently moving to Scaled Agile Framework which displaces Engineering Managers from Tech Leads to a bit of a meta role along the lines of career/team coaches (but not quite Scrum Masters which is a separate role...).

If we can solve staffing and performance reviews in the framework then the role can likely go away.

Re:How Google Sold Its Engineers on Management by esrauch on Monday April 20, 2015 @06:42PM (#9411293)
No offense intended, but I'm curious in whether you think there is actual expressive value in using those terms? I'm actually about 85% sure that your comment isn't a parody of buzzwords.
Re:How Google Sold Its Engineers on Management by cpeterso on Monday April 20, 2015 @05:17PM (#9410932)
Spotify has an interesting management structure of loosely-coupled "feature squads" and "guilds":

https://labs.spotify.com/2014/03/27/spotify-engineering-cult...