console.log("Does it happen here?")Stage 4.5: console.log() everything.
And then the logging fixes the subtle timing issue causing the problem.
Race conditions are the worst
Step 4.6: Get another drive for the logs.
We have logging software built in, but I can never remember how to turn it on, so I just console.log
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
Stage 7: Who wrote this?
Stage 8: Ah ok… it was me
How did that ever work, I’ve been there many times.
its funny i see this now, after spending 3 hours debugging D:
6 stages of dev grief when I find a bug which doesn’t make sense and report it to the devs. Lol.
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
“I notice that I am confused, and thus that one of my beliefs is fiction.”
One of the best pieces of advice I have ever gotten was to build diagnostics first. The time it takes to do will pay for itself 100X over the course of development.
100% unit tests ftw
Hate making them, love them when they are here
