I'm not saying you should just do random refactorings. What I am saying is that if you are fixing something, and realize that you can fix it while improving the code at the same time, it is typically worth it. Obviously if the refactoring is a huge undertaking, it's not going to be a great idea to pair it with a bug fix. But if your are smart about it, you can usually keep the code base clean/well-factored incrementally.

The problem with "quick" fixes is that they often end up being slower, because hacking a fix into a complex code base often creates new bugs/problems, and you end up rolling back your broken "fix".

> Only experience & practice give you ability to write good code.

I agree, which means that always writing shitty code to get it out the door means that you will only practice writing shitty code.

There's a balance to be found.