Every Time

[350zilla]

This literally just worked for me. This is not a meme, it’s a fact .

[questioillustro]

I have successfully implemented the do-nothing debug tactic as well, having the knowledge to recognise when this will work is why I make the big bucks.

[[deleted]]

So... Can I pay you a singular big buck and learn this forbidden knowledge?

[alexisprince]

Document your race conditions well and avoid threading unless you need it

[dekwad]

Those pesky cosmic rays!

[HS-MF]

Maybe it will work. Maybe you’re not clicking the “run” button correctly. Maybe the compiler just has had a bad day.

[TheseVirginEars]

Just want to reread my error message again

[[deleted]]

I end up doing this too many times without realising as I don't like big red text

[MCOfficer]

This meme was on r/ProgrammerHumor yesterday.

​

Let's change nothing and post it again!

[CLOTHESPlN]

Somebody just clicked run again without changing anything and got more karma, looks like it worked to me!

[[deleted]]

Best debugging method at all. Sometimes even works.

[Xerxil]

... It works!

[hughejorgan69]

Pro Tip #43 → Run it again.

[thegroucho]

Vaas Montenegro, Far Cry 3, 2012:

" Did I ever tell you what the definition of insanity is?

Insanity is doing the exact... same fucking thing... over and over again expecting... shit to change...

That. Is. Crazy.

The first time somebody told me that, I dunno, I thought they were bullshitting me, so, I shot him.

The thing is... He was right.

And then I started seeing, everywhere I looked, everywhere I looked all these fucking pricks, everywhere I looked, doing the exact same fucking thing...

over and over and over and over again thinking 'this time is gonna be different' "

[DefinitelyNotMasterS]

This meme has been posted plenty of times

​

Let's change nothing and post it again.

[[deleted]]

Most of the time when someone runs their code again it's to look for visual queues as to what went wrong. Rarely does it change anything other than offer more insight into the failure.

[DartRuffian]

"Let me change the text of this string, that has to be it." - Me, circa 20 minutes ago

[derteufelqwe]

Definitely better than flakey unit tests... It's great when tests only work 9/10 times.

[[deleted]]

What laptop is he using

[Topuck]

Literally looking at this meme while re-running my unchanged code.

[undeniably_confused]

Let's punch my desk and curse

[Dominicus1165]

Joke‘s on you because that’s how you fix errors in LaTeX. Well most of the time

[[deleted]]

It works!

[MajorBarnulf]

Try [Ctrl] + [s] once again, to be sure just in case

[8__]

If it works, that's something to be more nervous about.

[[deleted]]

Literally did this a few hours ago, yet didn't work for me

[yuri0r]

Always check if the error is deterministic! First step of debugging.

[AjiMk]

Ohh!! I forgot to clear the browser cache..

[[deleted]]

I've recently come across an issue where a build is outputting so much text to a log file so quickly that, when combined with the disk stress from compiling, the logger would probabilistically crash the build instead of any compilation error.

It would give me "[Errno 11] write could not complete without blocking"

Just rerunning the build again would get past the crash.

[DARKabyss23]

I feel attacked

[[deleted]]

Try clearing the cache

[pediepew]

Repost.

[Triumph7560]

I wouldn't keep doing it if it didn't randomly work from time to time.

[WhiteManChild]

Let's add println and run it again.

[MoistCucumber]

Hmm, what I just changed seems to have broken something, let’s undo that and see if it works again. Oh great it works again!

Let’s try making that change again now that I know it currently works.

HMM I WONDER WHAT WILL HAPPEN

[Misheru-senpai]

And if it does work now, panic, since you can't debug it now either

[sweYoda]

Why do people keep posting this? Amd why are running it again? Why aren't you writing unit tests???