Stage 4.5: console.log() everything.
And then the logging fixes the subtle timing issue causing the problem.
Race conditions are the worst
Good ol’ Heisenbugs.
We have logging software built in, but I can never remember how to turn it on, so I just console.log
Step 4.6: Get another drive for the logs.
console.log("Does it happen here?")Everyone always skips the last step, but that’s where you learn.
Every time that last part happens I have to check the proper spelling of Berenstain. I’ve had some that really seem like they should have been impossible lol
“I notice that I am confused, and thus that one of my beliefs is fiction.”
Get enough experience and you just have a brief moment of stage 3 as you dive straight to stage 4.
Unless it’s a customer/that-one-guy-at-work (it’s a title, but there’s usually a handful of them) and then there’s this vast stage 0 of back and forth of “are you sure that’s happening, run these commands and paste the entire output to me” to be sure of what they are saying then you jump to stage 3/4.
I jump straight to step 6
How did that ever work, I’ve been there many times.
I have some Excel VBA scripting that I’ve been on 1-4 for a while now, so there’s a branch off of 4 that should be “fuck it, here’s the workaround” or “that part isn’t that important anyway, ignore it”.
(it’s actually not Excel that’s the problem, it’s the change to its call to IE that throws up a stupid security warning.)
Oh my god this comment gave me an aneurysm
My boss does 1 <–> 2 with us over most every bug any of us has ever found. Ticking time-bomb…
its funny i see this now, after spending 3 hours debugging D:
As true as true can ever be
if (0 === 0) {
var_dump($test); die;
}Ahhhhh, PHP… 😭
if ((x != x) || (x == x+1)) then it’s one of those weird numbers
Stage 7: Who wrote this?
Stage 8: Ah ok… it was me
Has it ever!?
6 stages of dev grief when I find a bug which doesn’t make sense and report it to the devs. Lol.
