"Any time you have worked long hours, it is a sign of a broken process."
programmers.stackexchange.com
"Any time you have worked long hours, it is a sign of a broken process."
1–10 of 172 posts
Re: "Any time you have worked long hours, it is a sign of a broken process."
#2A lot of nice feel good answers on this post. But for some of us, too freaking bad if you have to work long hours.
I'm not personally a fan of long hours, but not everyone can work for a LinkedIn. And in many shops, long hours are unavoidable regardless of how much well-intentioned process is in place.
Re: "Any time you have worked long hours, it is a sign of a broken process."
#3A lot of nice feel good answers on this post. But for some of us, too freaking bad if you have to work long hours. I'm not personally a fan of long hours, but not everyone can work for a LinkedIn. And in many shops, long hours are unavoidable regardless of how much well-intentioned process is in place.
I realize it's rarely this simple, but get a new job if you care. The labour market is a market, and unless you leave, citing whichever of manager incompetence or lack of money is the problem, it won't get fixed because /it doesn't need to be fixed/.
Re: "Any time you have worked long hours, it is a sign of a broken process."
#4Routine long hours are sign of a broken process.
Rare spats of long hours due to abnormal events is not an issue
Re: "Any time you have worked long hours, it is a sign of a broken process."
#5I'm curious how efficient most coders are even in an 8 hour work day. I find that I can only log about 4 - 5 hours a day (on average) of solid coding time (or marketing/business work). This is because I limit myself to an 8 hour work day, but of course there are breaks and inevitable down time.
Re: "Any time you have worked long hours, it is a sign of a broken process."
#6This broken process ships a lot of games :(
Re: "Any time you have worked long hours, it is a sign of a broken process."
#7It'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-critical bug that has to be fixed by the end of the day or else all your customers will bail out?
Secondly, most who work in Wall Street will tell you it's not about the process. It's about the culture. People don't work until 7 or 8 because they're fixing bugs, or because development is so slow. It's because they're expected to and if they get up and leave at 5, it leaves a bad impression on management and their co-workers.
Re: "Any time you have worked long hours, it is a sign of a broken process."
#8A lot of nice feel good answers on this post. But for some of us, too freaking bad if you have to work long hours. I'm not personally a fan of long hours, but not everyone can work for a LinkedIn. And in many shops, long hours are unavoidable regardless of how much well-intentioned process is in place.
That is a sign of bad planning & bad management.
And software engineers' acquiescence to being abused like that ensures that it will continue.
Re: "Any time you have worked long hours, it is a sign of a broken process."
#9I know a lot of people who seem to like working long hours. It allows them to think they're getting more done, but I suspect that many of the processes involved could be optimized if they thought about it a bit. For me, I work long hours but it's spread out over the course of a day (so removing breaks/bs it's probably not much more than 40 hours p/wk), and I love what I do, so I do get a lot done (and it feels less like work than other jobs I've had).
For other jobs, like being a big firm lawyer, long hours are kind of baked in: You get paid a salary (a big one), the company you work for bills you out by the hour, person with the highest billables doesn't get fired. That's probably not likely to change, it's not a process problem per se, and I suspect there's plenty other jobs generally like that.
Re: "Any time you have worked long hours, it is a sign of a broken process."
#10Long hours are not always because of a broken process, or death march deadlines.
Many times when I have worked long hours, it was because I was really into the problem I was trying to solve, and didn't want to quit.