3 ms·
It's true that someone experienced and focused could work 35 hours and produce as much as (or more than) another person who is less experienced and more randomi
by boomzilla 12y ago
It's true that someone experienced and focused could work 35 hours and produce as much as (or more than) another person who is less experienced and more randomized putting in 80 hours. Start up workloads (for good or bad) is more suited the latter type of workers though. The main reason is most of the time, no one knows exactly what needs to be done in a start up. Yes, product road map changes monthly (or even weekly) and blockers come up every day. As a result, someone sticks around more will be able to respond faster to the changes.
I will never do more than 60 hours work week, and that will only be for a couple of weeks max to get something out of the door. So as a result, I'll never work for a start up that doesn't have a concrete product road map that I could understand and believe in.
- SomeCallMeTim 12y agoI disagree with your premise (that 80 hours a week is appropriate for a start-up). As an experienced developer (25+ years now), I'd put money on my code being more capable of pivoting quickly to a new product road map than the code of a less experienced developer. I've had clients/employers be amazed by how fast I could change fundamental behaviors of software I've worked on, and not because I put in 80 hours, but because the design starts out flexible, and I can adapt the work to the new requirements with minimal effort. Sure if you're ask your dev to make changes on a Saturday, the 80-hour employee will be there, but if he/she is still working on that major pivot by Monday, and I can make the changes in a few hours, and my code is more stable, then I still win. ;)