Spite/Fury has been a good one for me in the past, in addition to those.
"How in the fuck was this ever allowed to get to this point? There's no way we can keep up with this unless we change the approach. I'm automating this shit whether they like it or not."
Write an entire chunk of code to handle some edge case that shouldn't exist, but does because people are stupid and make typos on critical shit, in one single frustration fuelled fugue state.
Why work at a steady pace toward a quality product in a timely and low stress manner when you could instead be paralyzed by executive function until the last possible moment that you could still turn in a minimally acceptable product after working in a furious panic?
There is a sweet spot where you put it off a bit but think it through while stressing, then spend the time powering through it while leaving some time to spare in case you screw it up. Only took a couple of decades to get decent at estimating!
Do your part ahead of time and your lab partner texts you the day before that he can’t do his because his hotel doesn’t have WiFi and he can’t go outside in the rain. After he already didn’t help with the first report.