Reminds me of the "meanwhile back at the ranch" school of screenwriting: switch to your B story when your A story is at its peak of interest, and switch to your A story when your B story is at its peak. That way when you do switch back you won't have to work (too hard) to keep the audience's interest.
Love this whole thread. I thought I'd add a bit more for those who ended up in the same position I ended up in a little while back: if you're ever stuck in a position where you're forced to use an environment where you iterate so slowly that it takes days to a week to get from one error to the next error: take notes along the way as you go. Take notes about things which could be done differently if they weren't stuck a certain way. Not only does it neatly manage deadline anxieties, but it helps you build a map of friction points that are keeping things slower than you'd like, and it gives you the detail you need to slowly build cohesive and persuasive plans for improving the situation.
Of course, the optimal plan at that point could easily be for you (as it was for me) to leave the situation, but even so -- at least it makes that clearer!
Try to stop on a bug or error.
Same reasoning you cited with a bonus: when you come back in the morning, you'll have an error message to help you quickly pick up where you left off.