And the worst part is when it actually does and you have no fucking idea what went wrong before.

That's step zero: rule out black magic

Me: "Hmm... No... No the code is good, it's the compiler that's wrong."

runs again

Yeah, but sometimes it works.

The first is a surprise; the second is testing.

could be a race condition

i sometimes do that so i can inspect the error messages on a cleared terminal

One of my old programs produces a broken build unless you then compile it again.

Just had that happen to me today. Setup logging statements and reran the job, and it ran successfully.

======== 37/37 tests passing ========

The crazy thing is that sometimes this just works...

If that doesn't work, sometimes your computer just needs a rest. Take the rest of the day off and try it again tomorrow.

I often do this, but I always hit Ctrl-S before running it again. Shamefully, this probably works about 10% of the time. Does that technically count as changing nothing?

Well, duh! You need to use the right incantations!

Somehow higher than 0% success rate.

it's only dumb til it works

Sponsored by QA gang. Gotta make sure it's a 5/5 issue and not just a frequent issue

The definition of insanity is doing the same thing over and over and expecting different results.