Yeah😎😎😎

No, not at all. That way every program would be stuck at the "minimum running example" state or you would have horrible code stile or bad performance or other unpleasant things, no innovation, etc.
This rule only applies to things that are so unstable that every change could ruin it forever, like my current Raspberry Pi setup. So far it works with 100% reliability, but I don't know how or why and I've had many attempts before that didn't work for mysterious reasons.
But if you know what's going on in your code and you did that intentionally, then it's the exact opposite.

Absolutely incorrect. If it works, ok it's pretty good but maybe there is a better way to do it. Personally I had a similar experience.

The real 1st rule of programming: If it doesn‘t work after touching, it‘s shit!

This is only good advise if you want /r/badcode in your production environment.

@Fabian bro I'm agree with you.... I posted it as a joke.