When to remove hacks?

by Terry Hughes Friday, April 24, 2009 04:15 PM

A coworker of mine ran into a bummer of a problem and asked for advice. Over lunch we talked about what to do, I personally felt that option 2 was the safest solution. I didn't really like adding bad code to cover up bad code and I began to think about how you would know when the hack could be removed. Then I threw out the idea of writing a test to verify that the bad condition is present. When the test fails you will know to remove (or at least re-evaluate) the hack. He thought it was a neat idea, can't wait to see what he comes up with.

Tags:

Tips

Comments are closed

About Me

TerryH   I'm a senior software developer currently working for a small company specializing in case management software.

Page List

Disclaimer

The opinions and viewpoints expressed on this blog are not necessarily those of a cultured, tactful, or well-balanced person. This blog is a product of me, who is solely responsible for its content. Me - Stealing From Smart Developers.

Copyright © 2008-2009 Terry Hughes. All rights reserved.