December 5th, 2007
In my opinion, the worst developer’s excuse for bad code is: Â«I didn’t had much time, so I did everything the fastest way possible…Â». The problem is that this excuse is always present. Developers always have tight schedules, and sometimes they also have several tasks to do at the same time. The day-to-day stress frequently moves this excuse from being just an excuse to be something more like a development mindset.
And usually this fast development methodology translates to:
- A lot of copy paste
- No objects for the base project concepts, instead intrinsic types are used
- No unit tests or refactoring
I really don’t think that the lack of time is a good justification for bad code quality. In fact, I think that with proper analysis and good architecture, the development will be faster. The fast development methodology may be quicker on the short run, but everyone knows that maintaining this kind of code is very error prone and quite complex. And sometimes some simple modification will be very delayed just because things weren’t done right the first time.
When you have bad code, you’re sticked to it. It’ll never improve, unless you totally rewrite it. With no unit tests, no one will take the chance of refactor code that’s already working, and you’ll have the Â«can’t touch thisÂ» effect.