"Any time you have worked long hours, it is a sign of a broken process."
21–30 of 172 posts
Re: "Any time you have worked long hours, it is a sign of a broken process."
#22Routine long hours are sign of a broken process. Rare spats of long hours due to abnormal events is not an issue
But yeah, I appreciate the sentiment that no-one should be allowed to pillage their workers' evenings and weekends simply because they don't want to tell their boss "I promised something I couldn't deliver."
Re: "Any time you have worked long hours, it is a sign of a broken process."
#23Re: "Any time you have worked long hours, it is a sign of a broken process."
#24The amusing thing to me is that the question was closed as offtopic. Stackexchange is slowly turning into a Usenet/Wikipedia hybrid.
Re: "Any time you have worked long hours, it is a sign of a broken process."
#25This broken process ships a lot of games :(
I don't know how many hours Braids creator worked, but I have a feeling that it was a lot less than a deathmarch.
Re: "Any time you have worked long hours, it is a sign of a broken process."
#26It's nice that LinkedIn has a great process: regression testing and the like, but what if you work in an environment where you can't afford to test every single little thing, and where business models, let alone requirements change constantly (ie. a startup)? What if a competitor just launched a feature that will put you out of business if you don't implement the same thing in 48 hours? What if there is a mission-cri…
Re: "Any time you have worked long hours, it is a sign of a broken process."
#27It's nice that LinkedIn has a great process: regression testing and the like, but what if you work in an environment where you can't afford to test every single little thing, and where business models, let alone requirements change constantly (ie. a startup)? What if a competitor just launched a feature that will put you out of business if you don't implement the same thing in 48 hours? What if there is a mission-cri…
And what difference does it make to call it a cultural thing? People are still getting their heads injured.
Re: "Any time you have worked long hours, it is a sign of a broken process."
#28Routine long hours are sign of a broken process. Rare spats of long hours due to abnormal events is not an issue
Or even due to awesome coding. I would hate to miss out on my occasional bouts of can't-drag-me-away-from-the-keyboard inspiration simply because someone "fixed" my work ethic and shut the office at 5pm. But yeah, I appreciate the sentiment that no-one should be allowed to pillage their workers' evenings and weekends simply because they don't want to tell their boss "I promised something I couldn't deliver."
Re: "Any time you have worked long hours, it is a sign of a broken process."
#29Re: "Any time you have worked long hours, it is a sign of a broken process."
#30What do long hours often represent? Enterprise: Incompetent management, lazy co-workers, and spoiled users. Small Business: Tough competition and limited resources. Startup: Taking advantage of opportunites that may not pass this way again.
He's making the point that regular long hours are always a sign of bad management.
I'd tend to agree. Any business can be run in balance with a reasonable lifestyle. If you're working overtime very often on your own business, it's either because you're incompetent, or lazy, or greedy, or failing (see 'incompetent'). If you're working regular long hours on someone else's business, it's because they are incompetent/lazy/greedy.