![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Racing the computer
Coders, help me out by confessing so that I'm reassured I'm not the only one...
If you're working on a project that has a significant compile time (say, five minutes or so), and you set it going and then realize that you've forgotten to change one thing that you want to get in... do you stop it, or do you - as I do - seize the opportunity to prove your superiority, leave the compile running, zoom to the file in question, and race the computer to make the change and save the file before the build grabs it?
If you're working on a project that has a significant compile time (say, five minutes or so), and you set it going and then realize that you've forgotten to change one thing that you want to get in... do you stop it, or do you - as I do - seize the opportunity to prove your superiority, leave the compile running, zoom to the file in question, and race the computer to make the change and save the file before the build grabs it?