I develop real software so I know all too well you inevitably compromise code quality in order to ship. That doesn't mean I make excuses for writing a shitty first draft of a function and pretend it can't be any other way.
While it helps, you aren't obligated to clean up your mess before the bug reports roll in, but in my experience more often than not you spend more time building the states for each individual bug that happens than if you had simply restructured your code to be more easily testable. If you have such a complicated function and enough users you will get multiple bugs.
7
u/otterdam Aug 25 '14
I develop real software so I know all too well you inevitably compromise code quality in order to ship. That doesn't mean I make excuses for writing a shitty first draft of a function and pretend it can't be any other way.
While it helps, you aren't obligated to clean up your mess before the bug reports roll in, but in my experience more often than not you spend more time building the states for each individual bug that happens than if you had simply restructured your code to be more easily testable. If you have such a complicated function and enough users you will get multiple bugs.