3 ms·

> The bottom line is that there is too much code to maintain (or migrate, or rewrite, depending on the shape of your hole) and never enough resources/people/bud

> The bottom line is that there is too much code to maintain (or migrate, or rewrite, depending on the shape of your hole) and never enough resources/people/budget/time to do it. Everyone says this, but then finds time for FB/Twitter/HN during the day. Something doesn't line up. This is a question of priorities, and people not feeling the effects of hard coupling to a framework.

deleted 13y ago
[deleted]
x0x0 13y ago
do you really believe that 20 minutes of time wasting on hn per day somehow translates into a significant amount of dev work that I could have done but didn't?
- mattgreenrocks 13y ago
  20 * 5 = 100 minutes So, yes. It's OK if you don't, but I think it's worthwhile foregoing social media sometimes to work on studying and upping your game. Besides, you don't always have to be in "OMG not enough time to do this nicely!" mode. Such a mindset is reactionary and generally not conducive to writing robust code. I'd rather go a little slower and not have to return to parts of the codebase later.
  - pavel_lishin 13y ago
    Not all minutes are created equally. Spending 100 minutes in a row on code is usually pretty useful; coming back to it for 20 minutes a day is not, especially if we're talking about upgrading to a major upgrade of a framework, which we are.
    - icefox 13y ago
      I would have to second this. When I have a meeting that ends 15 minutes before lunch it is hard to want to work on a task when I know I wont be able to get into the flow.
doktrin 13y ago
> Everyone says this, but then finds time for FB/Twitter/HN during the day. Not to mention extravagant lunch breaks spent chewing food instead of inhaling Soylent, trips to the bathroom and time wasted milling around the proverbial water cooler. More to the point, the technical debt being discussed here isn't solved by increasing office productivity by 5%.
iopq 13y ago
This is why we don't do away with the 40 hour work week. Some people will always think that working more will solve all of our problems.
- mattgreenrocks 13y ago
  Haha, not at all. I'm all for 20 hour weeks. I do believe that thinking more and working less on work will solve more problems though.

deleted 13y ago

[deleted]

x0x0 13y ago

do you really believe that 20 minutes of time wasting on hn per day somehow translates into a significant amount of dev work that I could have done but didn't?

mattgreenrocks 13y ago
20 * 5 = 100 minutes So, yes. It's OK if you don't, but I think it's worthwhile foregoing social media sometimes to work on studying and upping your game. Besides, you don't always have to be in "OMG not enough time to do this nicely!" mode. Such a mindset is reactionary and generally not conducive to writing robust code. I'd rather go a little slower and not have to return to parts of the codebase later.
- pavel_lishin 13y ago
  Not all minutes are created equally. Spending 100 minutes in a row on code is usually pretty useful; coming back to it for 20 minutes a day is not, especially if we're talking about upgrading to a major upgrade of a framework, which we are.
  - icefox 13y ago
    I would have to second this. When I have a meeting that ends 15 minutes before lunch it is hard to want to work on a task when I know I wont be able to get into the flow.

doktrin 13y ago

> Everyone says this, but then finds time for FB/Twitter/HN during the day. Not to mention extravagant lunch breaks spent chewing food instead of inhaling Soylent, trips to the bathroom and time wasted milling around the proverbial water cooler. More to the point, the technical debt being discussed here isn't solved by increasing office productivity by 5%.

iopq 13y ago

This is why we don't do away with the 40 hour work week. Some people will always think that working more will solve all of our problems.

mattgreenrocks 13y ago
Haha, not at all. I'm all for 20 hour weeks. I do believe that thinking more and working less on work will solve more problems though.