Well, there probably is, however you have to ask yourself, is this really what I want.....?????
Here's the deal. If you use a "high-speed-bad-code-detector-gizmo", the question becomes
what have I learned from this....?
By going through countless iterations of the development cycle, enduring the "pain and suffering" of
trying to decipher other developers code, after awhile, (...and trust me on this one...)
will be able to spot "bad code", in most cases, right from the start.
I know, I know, time is of the essence in some software development organizations. Got to get it fixed and back in to production. Need an answer now.
Blah, blah, blah....
But in the longterm, as painful as it is, determining what "bad code" is, and how to identify it will come from the experience of going
through the software, determining better solultions
, and applying those solutions in future developments.
This is how us "old coots"
used to have to do it. Just depends on what you want and how you want to do it......
Edited by Imperious Leader, 19 November 2009 - 11:07 AM.