Spyke
sh.itjust.works

Cheer the computer along every step and offer motivational speeches

10

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.

9

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.

6

Obligatory XKCD

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.

6

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...

5
sh.itjust.works

To be fully effective with your time, go get a cup of coffee first, and then start the compiler. ;-)

4

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)

4

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.

3

Browse hacker news or perhaps lemmy now. It’s not really enough time to switch to doing something productive now is it?

2
pax
u.fail

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.

2

I can recommend neovimtpo you it is more accessible then normal vim

1

You reached the end

What do you usually do if the compile time is something like 15 minutes? | Spyke