sometimes you don’t compile it enthusiastically enough
Ah, come on this is valid investigation.
If you get the same error every time, you know you can find it and debug it, somewhat with ease.
If you don’t, you might have a thornier issue at hand.
Because you’re Good developer
I started coding professionally using Visual Basic (3!). Everybody made fun of VB’s
On Error Resume Next“solution” to error handling, which basically said if something goes wrong just move on to the next line of code. But apparently nobody knew aboutOn Error Resume, which basically said if something goes wrong just execute the offending line again. This would of course manifest itself as a locked app and usually a rapidly-expanding memory footprint until the computer crashed. Basically the automated version of this meme.BTW just to defend VB a little bit, you didn’t actually have to use
On Error Resume Next, you could doOn Error Goto errorHandlerand then put theerrorHandlerlabel at the bottom of your routine (after anExit Sub) and do actual structured error handling. Not that anybody in the VB world ever actually did this.demonsahem. data-races.This is just how you use Visual Studio
The absolute worst thing that can happen is if it suddenly starts working without doing anything
Sweet, push to production.
sometimes it needs to warm up… or cool down
Trying to debug race conditions be like
Yuuup… Debugging concurrent code is a bitch.
You make a change. It doesn’t fix it.
You change it back. The code now works.
The code now
worksbreaks in a new way.the real fix was the journey, the destination never mattered
The error message goes stale when it’s been sitting for a while. I need to see a fresh one.
When your
Makefileis so fucked up that you have to run it multiple times to get everything to build and link properly.Just making sure that the write buffer was flushed on time or something.
Or the code you are working on is calling a system that is currently unreliable which you cannot be responsible for.
Fuck test automation, it’s a fucking trap get out of it as soon as you can
Fuck test automation, it’s a fucking trap get out of it as soon as you can
lol.
Meanwhile, the org I work at has no test automation, so things that should be trivial require hours of tedious, error-prone, manual testing. Also they break stuff and don’t find out until after it’s merged.
This post has appeared in multiple places. It’s useful , but it ruins the development career potential of people that stick with it, because any subsequent job application just sees “TESTER” and not “DEVELOPER” and bars you from changing specialization.
I’ve known several people who moved from QA and testing to developer roles, but usually as an internal transfer.
Most recruiters and management don’t know shit about fuck when it comes to technical details, so it’s not surprising a lot of them think “Oh the guy who knows how software works and how to handle edge cases? No, we don’t want him”
Code doesn’t work; don’t know why.
Code works; don’t know why.
Cargo Cult Programming is bad.
