31–40 of 172 posts
I'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.
I 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 l…
I know at my rates, if I work 14 hour days, my productivity shoots down, and I blow the face and upper body off the budget in no time.
I 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 l…
I know at my rates, if I work 14 hour days, my productivity shoots down, and I blow the face and upper body off the budget in no time.
I 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 l…
I know at my rates, if I work 14 hour days, my productivity shoots down, and I blow the face and upper body off the budget in no time. I tell people this, but they still want it sometimes. But really, it's usually better to cut expectations and go at a measured pace all the time.
I 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 l…
I know at my rates, if I work 14 hour days, my productivity shoots down, and I blow the face and upper body off the budget in no time. I tell people this, but they still want it sometimes. But really, it's usually better to cut expectations and go at a measured pace all the time.
Ah, so this is why it takes LinkedIn forever to add new features.
Long 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.
Yes, precisely. This only applies if you were forced to work the long hours, as opposed to doing it because you felt like it.
I'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.
I 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 l…