Thursday 17 October 2013

Premature Obsolescence

G'day:
An online mate of mine just pointed me at some code he was fixing (not his own, I hasten to add), and drew my attention to some code commentary which made him laugh / cry / scowl / despair:


<!--- Sorry, I know it's bodgy, but this site won't be around much longer... --->

Which it itself is a bit rubbish. That's no excuse for bodgy work. Just do the job properly. Code the correct solution for the current situation all the time.

The thing that makes this worse is this. The comment also had a date:

<!--- 2008-04-09 @ 13:16:33 PM [NAME REDACTED] Sorry, I know it's bodgy, but this site won't be around much longer... --->

2008. So that soon-to-be-retired site is still up and running now, 5.5yrs later.

This is cowboy's version on "premature optimisation"... basically "premature shit workmanship".

I will bear this work in mind if I ever cross paths with the individual concerned (which is entirely likely, given the size of our community).

Don't write shit code. Do your jobs properly. Writing shit code just makes you look shit.

Righto.

--
Adam