When is code good enough?

The most recent blog post about the newest release of jQuery got me thinking about some of the code I've been writing. In the post, they have this little gem:
We don’t expect to get any bug reports on this release, since there have been several betas and a release candidate that everyone has had plenty of opportunities to thoroughly test. Ha ha, that joke never gets old. We know that far too many of you wait for a final release before even trying it with your code. So now there is really no reason to wait, and you can find out if there are any bugs you could have reported earlier.
I've been searching high and low for any anomalies in the code and when I see some code that's not "up to code" I reformat and refactor as necessary. Which is to say, as I find bugs, I've been getting them fixed, but at other times, I'm simply making changes to the codebase to adhere to a particular style that I've been working toward. I suspect I should probably stop some of that "cleaning up for the sake of cleaning up" and let the testing continue as necessary, but I'm finding it difficult to do. 
With the bugs that I do find, in most cases, I have *not* included tests (shame on me) due to the complex nature of the code and little time to refactor something of that magnitude. You see, we're getting down to the last few weeks of testing before pushing this beast to production, so I'm doing my best not to tweak code. 
During this time, I am finding my OCD tendencies are difficult to repress. The thing about the post from jQuery, however, makes me feel a little bit better about not getting the codebase to complete bug-free as that's a Utopian place that might never be found. Anyway, I'm feeling a bit more relieved about the current state of affairs with regard to the code I've been working on for the last year or so. However, that doesn't make me any less nervous about pushing this thing to production...

Comments

Popular posts from this blog

Adventures in Getting a Site Hosted

Using Bogus to create Hierarchical Data Structures

Design Patterns: An Introduction