3 ms·

I have a unpopular opinion, goes against the main theme of this thread. I find the "go the fuck home" strategy works for projects where output can be correlate

I have a unpopular opinion, goes against the main theme of this thread. I find the "go the fuck home" strategy works for projects where output can be correlated with time spent. I'm in a situation where we're in new terrain, we're hitting problems that haven't been encountered before in our space. To fix them properly, I need to do a deep dive and fix the root cause, this takes time, time which seems to never exist. Its quite insulting when someone says, "You can't get done this between 9-5, so you're incapable of doing this job." Have you guys been in this type of a grind? I'm not sure how to deal with this right now other than fixing the core issues and moving on, which basically means working even more.

mattmurdog 11y ago
This is extremely valid.
pfranz 11y ago
This just sounds like "context switching" is your problem (I have the same problem where I work), instead of the number of hours you work. That's a well know productivity killer for programmers. If your job is flexible about the hours you work I think that's a separate issue than what's discussed here. Work late and come in late the next day or come in early and leave early. Maybe there's a few core support hours in the middle of the day where you need to be reachable for meetings or something. I'm thinking about trying to implement a "quiet time," an hour or a few hour window everyday where you can expect some radio-silence. Even if it's once or twice a week I think it'd help.