I read the code I just wrote before finding out I have some issue meaning I'll have to re-compile, 20 minutes in.
Edit: Oh shit, you likely mean not my own code. In that case I just read their code and pretend I know what's going on.
Non-meme answer: something light, like read the news headlines, check some emails. Basically, I don't want to burn too many of my mental cycles while the cpu burns many.
The first and most important step is to go grab a cup of coffee. After I just waste time doing other stuff, like browsing reddit lemmy.
To be fully effective with your time, go get a cup of coffee first, and then start the compiler. ;-)
Run make -j<insert number of CPU cores here + 1> Overclock If all else fails, go make a coffee (or go make a coffee anyway)
That's what the second monitor is for.
Which means the actual answer is miss the sudo prompt for a password and time out the update...
Lol, compile times are usually like at least double that on the hardware I run 😂.
I just usually visit reddit, or in the last week or so, Lemmy. Sometimes I do code/script corrections, but rarely to be honest.
I just press cmd+n on terminal window and then type ~/tdsr/tdsr, to start tdsr then I open some code to see if I can find a way to fix my stupidly borked prototype, with nano, if I can't find where tf I made a mistake: I open visual studio code, the most accessible code editor that exists.
Browse hacker news or perhaps lemmy now. It’s not really enough time to switch to doing something productive now is it?