sometimes it needs to warm up… or cool down
Trying to debug race conditions be like
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 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.
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”
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.
… try it now.
Computer needs practice to get program right.
gotta rule out cosimc rays flipping a bit or two
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.
This would be more mockable if it didn’t often WORK.
