You ever fix a bug by doing absolutely nothing?
Like, the code just decides to work again.
No changes. No commits. No reason.
Just vibes.

And now I’m terrified to touch anything because apparently my codebase has emotions.

Probably concurrency issues.

This guy explains it perfectly: https://youtube.com/watch/...

Just ensure your code base is not bipolar.

Usually a race condition, or an environment setting.

So a Computer Scientists, a business man and an engineer go on a trip. It's snowing and the brakes go out. They are skidding around and finally get the car under control and get to a stop.

They get out and the business owner says "I know a guy up the hill with a tow-truck that can get us back on the road in no time." The engineer said, "Well pop the hood first. I want to know what happened." The Computer scientist says, "eh it was probably just a fluke. Let's get back in the car and see if it happens again."

I've heard people call it a heisenbug

A computer bug that disappears or alters its characteristics when an attempt is made to study it.

https://blog.codinghorror.com/new-p...

@donkulator fell for the trap lmao