You know what this is based AF because if you don’t do it a second time how would you know if it wasn’t a weird edge case or a race condition or maybe you just didn’t internalize the cause and effect because you weren’t looking for it until a bug appeared
Far worse, and this applies to more than programming. If something is broken, I want it to be consistent. Don't fix yourself, or sort of work but have a different effect. Break, and give me something to figure out, damn it.
Honestly, in DevOpS, when you’re running stuff in a GitHub Action/Azure DevOps Pipeline/Jenkins, yeah… sometimes a run will fail for no obvious reason.
And then work the next time (and the next 100+ times after that) when you haven’t changed a damn thing.
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 about On 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 do On Error Goto errorHandler and then put the errorHandler label at the bottom of your routine (after an Exit Sub) and do actual structured error handling. Not that anybody in the VB world ever actually did this.
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"
JavaScript is what is called an interpreted language there is no compiling at all the code is directly read and interpreted at runtime. Most of the time it's minified which reduces the size. Or in the case Vue React or Angular is transpiled which still results in JavaScript code but framework specific syntax is broken out and it's ran through bable to do backwards compatibility for older browsers.
xkcd 242 obviously
I feel called out. I'm not sure which way I'd go.
Get somebody else to pull it.
For science.
Me playing point and click games
You know what this is based AF because if you don’t do it a second time how would you know if it wasn’t a weird edge case or a race condition or maybe you just didn’t internalize the cause and effect because you weren’t looking for it until a bug appeared
But sometimes it works, or throws a different error ...
And a different error means progress!
A different error each time?
I refer to @[email protected] comment.
When it does a different crazy thing every time and you have no idea why, it means you're a genius and have created life.
Or you’re coding in C.
Actually tru. Damn preprocessors.
you have to check if you are dealing with a bug or with a ghost
You make a change. It doesn't fix it.
You change it back. The code now works.
the real fix was the journey, the destination never mattered
The code now
worksbreaks in a new way.The usual for me is that I flip back over to my editor and hit ctrl+save, cause heaven forbid I ever remember to do that before running.
I have no regrets from setting my editor to save-on-blur
Trying to debug race conditions be like
Yuuup… Debugging concurrent code is a bitch.
The first one is to warm up the engine. Like getting your car ignition to kick over in the winter
and sometimes that's exactly what's needed. Services wake up, connections get established and then when you try again things are up and it works.
Code doesn't work; don't know why.
Code works; don't know why.
Cargo Cult Programming is bad.
The absolute worst thing that can happen is if it suddenly starts working without doing anything
Sweet, push to production.
The error message goes stale when it's been sitting for a while. I need to see a fresh one.
Not sure which is worse. When you know you changed nothing and it inexplicably starts|stops working compared to yesterday
Far worse, and this applies to more than programming. If something is broken, I want it to be consistent. Don't fix yourself, or sort of work but have a different effect. Break, and give me something to figure out, damn it.
You know, youve gotta give your computer some warmup.
Running the code again is fast and requires no thinking. Finding the problem is slow and requires a lot of thinking.
It's worth looking under the light-post in case your keys somehow rolled there. Just not for long.
You jest but “wait and retry” is such a powerful tool in my DevOps toolbox. First thing I tell junior engineers when they run across anything weird
Honestly, in DevOpS, when you’re running stuff in a GitHub Action/Azure DevOps Pipeline/Jenkins, yeah… sometimes a run will fail for no obvious reason.
And then work the next time (and the next 100+ times after that) when you haven’t changed a damn thing.
"Maybe if we ignore the problem, it will go away"
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.
I hate how stupid and obvious this is, but we all do it at least once if the compile is short. But with a 20 min compile, I am investigating.
Computer needs practice to get program right.
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.gotta rule out cosimc rays flipping a bit or two
This would be more mockable if it didn't often WORK.
Just making sure that the write buffer was flushed or something.
When your
Makefileis so fucked up that you have to run it multiple times to get everything to build and link properly.And run it with the debugger.
sometimes it needs to warm up.. or cool down
sometimes you don't compile it enthusiastically enough
This is just how you use Visual Studio
Because you're Good developer
demonsahem. data-races.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
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"
yeah. My current company botched mine.
... try it now.
This genuinely happens regularly in our testing environment 🥲
does it count if i run it again, but with a debugger attached?
Most applications aren't written to compile deterministically so there is always a chance.
Compile? Is that true? Pretty sure compilers are generally deterministic in their output.
Mainly making a joke that they aren't binarialy deterministic. Semantically they are though. https://blog.onepatchdown.net/2026/02/22/are-compilers-deterministic-nerd-version/
Hmmm would most code these days be compiled into minified JavaScript? That might be more deterministic.
JavaScript is what is called an interpreted language there is no compiling at all the code is directly read and interpreted at runtime. Most of the time it's minified which reduces the size. Or in the case Vue React or Angular is transpiled which still results in JavaScript code but framework specific syntax is broken out and it's ran through bable to do backwards compatibility for older browsers.
Isn’t Typescript compiled into JavaScript?
Technically transpiled. Compiling results in something binary.
No a compiler just translates from one language into another. Transpilers are a type of compiler.