14 ms·
* Product is successful * Hire lots of people because that's what successful companies do * Product development slows way down, because you hired too fast (My
by Trasmatta 7y ago
* Product is successful
* Hire lots of people because that's what successful companies do
* Product development slows way down, because you hired too fast (Mythical Man Month stuff kicks in, where adding more people to a team can slow development down, if not done carefully and thoughtfully)
* Notice that development is slow, so you hire even more people to try and speed it up
At least that's been my experience at 3 different companies.
- mrnobody_67 7y ago100% correct. I love the Carta philosophy on hiring - every person you need means you've failed to execute: https://carta.com/blog/how-to-hire/ https://carta.com/blog/how-to-hire/ Unfortunately they didn't heed their own philosophy given their layoffs with simultaneous massive fundraise.
- deleted 7y ago[deleted]
- whatshisface 7y agoA healthier dynamic with the same result: - Value of a 1% improvement at $100/week revenue: $104 of developer time. - Value of a 1% improvement at $1M/week revenue: $1,040,000 of developer time.
- sk5t 7y agoHiring too much is a problem, but also bear in mind that having customers sort of gums up the works--you can't go changing stuff on a whim without communication, more careful assessment of impact, migration plans on customers' schedule--it's easier to be nimble when there's nothing to conserve.
- nikanj 7y ago* Product isn't that complicated at heart, so new hires busy themselves with complicating it, to justify their paychecks * Your easy to manage monolith is now seventy-three microservices, in case you need to serve Google levels of traffic without any further engineering. You're hopelessly understaffed to keep the monstrosity stable, so now you've got to grow your engineering corps to Google scale.