What if every bug report, valid or invalid, required a test case, per Test Driven Development?
Unless it’s a transient, unrepeatable hardware fault, it’s not a glitch – it’s a bug. Glitch makes it sound like it’s nobody’s fault. And glitches don’t stop all banking transactions for a number of days, that’s a top-to-bottom fuck up – or bug, take your pick.
And for that matter, if legal restrictions prevent parties from being identified, it’s “mustn’t be named”, not can’t.
JWZ has observed he now mostly programs because of things that piss him off.
In Coles on the weekend, I bought (from an enormous stack) this season’s Fruit Mince Pies.
At the start of August.
Only five months to go before this particular seasonal treat is only on the shelves for a couple of post-Christmas months as stocks are wound down.
This is getting ridiculous.
In the future, damn it!
If you have an ACS-15 digital scale beeping and flashing error code L6 on the LED display, I think it means “battery undercharged, and I refuse to work until it’s better charged. I don’t care if you plug me into the mains.”
And now Google knows. I wonder where I put the instructions?