Sloppy code. We’ve all seen it, and the problems it can cause. Whether that is not thinking things through fully (ie: no impact assesment), simply being careless and slapdash when it comes to writing code (ie: don’t care or in a rush to get it out), or even the programmer being as thick as two short planks (ie: should be digging holes for a living), the results can be pretty much the same.

I know one ‘programmer’ who doesn’t even compile code after writing it. They just hack it together, check it back in, and sit back with their feet up scoffing pies. Of course more often than not it wouldn’t actually compile, and it needed somebody else to fix their fix. Thus wasting everybody’s time.

(more…)