4 ms·

I don't think that the number of hours per day/week is particularly important. It's important to distinguish between efficiency and effectiveness. There's been

I don't think that the number of hours per day/week is particularly important. It's important to distinguish between efficiency and effectiveness. There's been times where I've spent weeks or even months going down a path that has ultimately proven fruitless, including spending really long hours on it. That certainly counts as work, but if it results in no meaningful value being produced, then what's the point? There's been other times when I've gone on holiday and come back refreshed and incredibly motivated, having realised the solution to a problem that I'd been struggling with because I gave my subconscious mind time to do its thing without interruption. Does spending time at the beach, exploring ancient towns in Italy, or even just taking a shower count as work? Most people would say no, but that's when I've had some of my best ideas. Sometimes in a meeting I'll be having a discussion with a colleague and we'll come up with a solution for something we've been trying do that requires zero changes to the our codebase, something we refer to as a "no-code" solution. Those can shave off weeks of time. Technically, that meeting counted as two hours of work; is that less productive than spending a ton of time implementing a feature that turned out to be unnecessary because there was a way to avoid the need for it? As far as when I actually sitting at my desk focusing on work, I value reading and thinking much more than implementation. Coding is the easy part; once the solution is clear, getting it into the computer is fairly straightforward, albeit quite tedious. I've spent lots of time coding the wrong thing, which with a bit more thought and research could have been avoided. I consider that time mostly wasted, except perhaps for the learning experience. Judge your productivity by what you achieve, not how long it takes you to do it. Edit: A thought experiment I'd like to add. Imagine you give two people the same task and ask them to complete it in one week. One person works on it four hours a day, the other six. They both get it done on time, at the same level of quality. The first person was actually _more_ productive than the second.

CodeGlitch 6y ago
Some great advice here.
kd5bjo 6y ago
> Imagine you give two people the same task and ask them to complete it in one week. One person works on it four hours a day, the other six. They both get it done on time, at the same level of quality. The first person was actually _more_ productive than the second. I'd argue that they were equally productive. To be more productive, they'd have to produce more work product during the week. Especially if it's a primarily mental task, there's a good chance that the 4-hour / day person is actually making progress when they're not visibly working, which would interfere with any attempts to either move the deadline earlier or get other work done in parallel.
- loco5niner 6y ago
  I guess it depends on what the first person did with their extra 10 hours.
therm0 6y ago
>There's been times where I've spent weeks or even months going down a path that has ultimately proven fruitless, including spending really long hours on it. That certainly counts as work, but if it results in no meaningful value being produced, then what's the point? how do you do this and not get fired? i got a lecture earlier this year about how spending two weeks on a difficult problem in a project that i'd just gotten dropped into was not befitting of a senior software developer.
- mjrbrennan 6y ago
  This is super workplace dependent. Some places just want you to churn stuff out quickly and are unforgiving of research and time spent thinking things through. Other places value everyone taking their time, learning, and finding the right solution, even if it takes longer, rather than the solution that works right this second.
- peterkelly 6y ago
  Communication is key. Once you've started working on something and it looks like it might not work out or take a lot longer than expected, discuss this with your manager and find out how they would like you to proceed. My approach is to make my case for why I should keep working on a particular thing (especially if I feel strongly about it and/or confident I can make it work given enough time), but ultimately respecting their decision. I find this works well. The cases where I've spent weeks/months on something are either where I was in charge of the project (during grad school, and later as an indie developer), or as an employee where my manager considered the task to be of sufficient importance to the business to continue down the path, even if it means spending more time or trying a few different approaches until I find one that works. This is especially the case with research-oriented projects where you don't know where a path is going to lead until you go down it.

CodeGlitch 6y ago

Some great advice here.

kd5bjo 6y ago

> Imagine you give two people the same task and ask them to complete it in one week. One person works on it four hours a day, the other six. They both get it done on time, at the same level of quality. The first person was actually _more_ productive than the second. I'd argue that they were equally productive. To be more productive, they'd have to produce more work product during the week. Especially if it's a primarily mental task, there's a good chance that the 4-hour / day person is actually making progress when they're not visibly working, which would interfere with any attempts to either move the deadline earlier or get other work done in parallel.

loco5niner 6y ago
I guess it depends on what the first person did with their extra 10 hours.

therm0 6y ago

>There's been times where I've spent weeks or even months going down a path that has ultimately proven fruitless, including spending really long hours on it. That certainly counts as work, but if it results in no meaningful value being produced, then what's the point? how do you do this and not get fired? i got a lecture earlier this year about how spending two weeks on a difficult problem in a project that i'd just gotten dropped into was not befitting of a senior software developer.

mjrbrennan 6y ago
This is super workplace dependent. Some places just want you to churn stuff out quickly and are unforgiving of research and time spent thinking things through. Other places value everyone taking their time, learning, and finding the right solution, even if it takes longer, rather than the solution that works right this second.
peterkelly 6y ago
Communication is key. Once you've started working on something and it looks like it might not work out or take a lot longer than expected, discuss this with your manager and find out how they would like you to proceed. My approach is to make my case for why I should keep working on a particular thing (especially if I feel strongly about it and/or confident I can make it work given enough time), but ultimately respecting their decision. I find this works well. The cases where I've spent weeks/months on something are either where I was in charge of the project (during grad school, and later as an indie developer), or as an employee where my manager considered the task to be of sufficient importance to the business to continue down the path, even if it means spending more time or trying a few different approaches until I find one that works. This is especially the case with research-oriented projects where you don't know where a path is going to lead until you go down it.