Re:Why you should never ask permission to clean up code.
by jodrellblank on Wednesday March 23, 2011 @01:23PM
(#2360330)
It's not just poor code which does it, it's code that has become tangled due to subsequent extensions and interactions.
Also, hopefully after a few months of project and codebase specific work, better ways to do what you did will start coming to mind - that's not the same as being a poor coder in the judgmental sense.
If you occasionally need to hack something out to ship it before its effect is lost — go for it. Clean it up the next time you touch it.
If you're constantly writing code under pressure like this, you have a management problem. Your boss probably doesn't code. Sucks for you.
If someone constantly ships poor code, you have a talent problem. Mediocre talent can kill a startup. Get rid of the bad apple ASAP.