sometimes it needs to warm up… or cool down
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
Trying to debug race conditions be like
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 or something.
Me playing point and click games
I feel called out. I’m not sure which way I’d go.
Get somebody else to pull it.
For science.
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”
But sometimes it works, or throws a different error …
Actually tru. Damn preprocessors.
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.
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
Computer needs practice to get program right.
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.
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.
