3 ms·
There seem to be at least two more cases that I've experienced that aren't on your list: 1. You're learning something new. It will take you X hours of practic
by nostrademons 17y ago
There seem to be at least two more cases that I've experienced that aren't on your list:
1. You're learning something new. It will take you X hours of practice to learn it, so if you want to get to the good part and be able to start building cool things with it, might as well get X out of the way.
2. You've got this burning idea for how to do something cool, and if you rest it'll leak out of your brain. Better get it done fast before the inspiration dries up.
There was a period a couple months back where I was pulling 12 hour days and working weekends for about 3 weeks. I had something that needed to be finished, and it was complicated enough that I feared that if I set it aside for anything, I wouldn't be able to load the problem back into my head. So I just did it, spending whatever time it took to get it done.
And then I spent a week or two working 6-7 hour days. I don't keep score, and I don't think my boss does either. From his POV, the project got done, and that's a win for him. From my POV, I didn't have much planned that month anyway, and my employer has been remarkably flexible when I need to take long periods of time off work, or need to leave early and work a shortened day, or just want to come in at 1 and leave at 10.
I won't sacrifice things that are important to me for my job - if an old friend is coming into town and I've got dinner plans with them, I'm not willing to be tied down to my desk. But if it's just a matter of writing some more code or blowing a few more hours on Reddit/HackerNews, I don't really mind writing the code so much.