Hacker News new | past | comments | ask | show | jobs | submit login

> I've argued before with my leadership that, if we really wanted something done better/faster, we shouldn't be promoting the folks that did it out of the position for the next go around

This is similar to what Fred Brooks suggests in the "Surgical Team" chapter of "Mythical Man Month", although he's a bit harsh, I'll grant that:

> if a 200-man project has 25 managers who are the most competent and experienced programmers, fire the 175 troops and put the managers back to programming.

EDIT: We were also talking about it yesterday here at HN: https://news.ycombinator.com/item?id=19763562




And not forget to fire those other managers who never wrote a single line of code.

Or anyone who thinks in terms like 'programmers' and 'resources'.


Brooks idea was even more radical:

Put non-coders to work under the chief programmer. Let them help instead of control.


That makes total sense to me. Having engineers in charge of the challenges that require engineering.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: