3 ms·
The problem is that the only easy to measure number is the number of hours worked. In the end you can't really measure output or quality so management will reso
by maxxxxx 10y ago
The problem is that the only easy to measure number is the number of hours worked. In the end you can't really measure output or quality so management will resort to the only concrete number they have. My output is highest when I work around 4-5 hours a day with occasional 24 hours marathons when things really flow. But I can see how this would make managers nervous because they can't really tell if I am just lazy or working at peak performance.
- notheguyouthink 10y agoI also imagine it would change workflows a lot for many companies. For example, my current company is very small and young (in experience). We're only now implementing meaningful workflows of builds, deploys, ci, etc... hell, even version control as previously an after thought. With that said, trying to increase staff heavily to compensate for 15h work weeks would mean a lack of workflows would impact us greatly, imo. Ie, some people here don't document their in progress work, and barely commit. How is someone else supposed to pick that up mid way through? Ie, the project still needs to get done in say, 2 weeks, but the original 40h/week dev will not be able to finish it in 2 weeks, so other people have to join in and work on it together. I'm not arguing against 15h weeks, just that it would mean single developers can't deliver the same product in the same timeframe most likely. So documentation, testing, and team communication would have to pick up the slack i imagine.
- noxToken 10y ago> with occasional 24 hours marathons when things really flow How on earth can you do that? A few weeks ago, I was in the office for 9 hours. I went home, goofed off of a little bit, then picked it back up for another 6 hours. I had been crushing it that day, and I was motivated enough to continue. In the wee hours of the morning, I was practically useless. I was hunting a bug that I had introduced with a small change. I reduced my statements to simple variables, created a truth table, then filled in the table to find equivalent statements. I was arguing with that damn truth table for half an hour. I lost of course. A truth table is a concept that can't be wrong. In fact, my conditional had been correct all along. It was a mapping that I had introduced elsewhere that was causing the conditional to evaluate differently.
- maxxxxx 10y ago"How on earth can you do that?" I don't do this every week or month but sometimes you struggle with something for weeks or months and then suddenly everything clicks and it just flows.