4 ms·

Perhaps, but I've fallen both in and out of this mindset, so I think it might have more to do with your state of mind. In my mind at the time, something needed

Perhaps, but I've fallen both in and out of this mindset, so I think it might have more to do with your state of mind. In my mind at the time, something needed to get done. And I was the only one that could do it. And I'm too proud to admit failure, so damn the torpedoes, and full steam ahead, about a weeks worth of no sleep, caffeine induced, coding frenzy. Both before and after that experience however, I'm the opposite. Unless it's a task that I own, and I feel like I NEED to do, and won't rest until it's done, then it's whatever man. Let me sleep. So for my situation, maybe it's all about getting yourself into that mindset and hyping yourself up for something. (Though all things considered, I was mega burnt out after what I did and would not ever try it again.)

fweespeech 11y ago
Perhaps. Out of curiosity, were you doing something that had a high-cost-per-defect? [e.g. All bugs lead directly to a loss of money for the company and/or accounting uncertainty on exactly where the money/inventory went]? The reason I ask is generally the only people I ever see saying stuff like that tend to be engaging in projects with low-risk-defects that don't translate to 4-5 figures of financial losses per defect but rather a "meh, I'll spend an hour later figuring it out and it costs me basically $0" kind of defects.