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
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 an team 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.
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”
Trying to debug race conditions be like
Yuuup… Debugging concurrent code is a bitch.
sometimes it needs to warm up… or cool down
Just making sure that the write buffer was flushed on time or something.
When your
Makefileis so fucked up that you have to run it multiple times to get everything to build and link properly.… try it now.
The error message goes stale when it’s been sitting for a while. I need to see a fresh one.
This is just how you use Visual Studio
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 …
Actually tru. Damn preprocessors.
you have to check if you are dealing with a bug or with a ghost
And a different error means progress!
A different error each time?
I refer to @floofloof@lemmy.ca 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.
This would be more mockable if it didn’t often WORK.
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.
The absolute worst thing that can happen is if it suddenly starts working without doing anything
Sweet, push to production.
