Why is it that every code push to fix one bug makes 3 more 🙃

All substantially complex code has bugs, imo. Changes just stir the bugs around to ones that don't conflict with your use cases.

I'm using the product manager's definition of 'bugs' here. :p

Sub-rant: I get pretty annoyed when I'm assigned bug tickets that are what I would consider brand new features.

@bezorp "it's not broken, I like it that way" some people just like to see problems.

"An action produces an equal and opposite reaction" - issac newton

"A single bugfix produces thrice the amounts of bugs" - every programmer ever.

Its just a proven law of nature, we can't do much 😉

In any very complicated system the interactions between parts can have very complicated outcomes. Changes in behaviour may not just propagate but multiply through the related stages

Lots of programming practices are about coding in a way which should prevent that from happening. The simple example being having a value defined in a single place and the symbol reused everywhere so that you do bit need to hunt down values.

Things like unit testing, integration tests and system level testing (hopefully automated) will help you spot some of your new bugs early. They are unlikely to get everything and there is high initial time cost. Especially considering that doing your job near perfectly should mean it all works first time 😂

That or it is just job security by some devs sneaking in future work to do 😜