3 ms·
I think what he was going for was that you shouldn't solve the overworked problem with hiring. It indicates you need more manpower, yes, but it's also indicativ
by foobarchu 9y ago
I think what he was going for was that you shouldn't solve the overworked problem with hiring. It indicates you need more manpower, yes, but it's also indicative of planning and resource allocation problems that need to be solved first. Adding more people before you solve those problems will probably make things worse. Things need to be properly divided and conquered, some things may need to be put on the back burner. It often indicates that you haven't split up the workload into manageable pieces, and are instead trying to get it all done at one time.
Someone might now jump and say 'sometimes crunch time is necessary!', and I would reply that if you're in crunch time you've just demonstrated the exact issue I'm describing.
I think he's essentially restating 'the mythical man month' for a modern environment.
- Bahamut 9y agoBut similarly, quickly coming to the conclusion to not hire is just as fallacious. If someone burns out as a result of the bungled planning, then the project can potentially be doomed without hiring (or even doomed anyway) - one should almost immediately reevaluate when one comes into this situation unless there was some sort of agreement beforehand.
- nerdponx 9y agoAlternatively, feeling pressure to hire because of workload means that you failed to hire quickly enough upfront, and now you are manpower strapped because you were trying to make your burn rate look better for this month.