For crying out loud! Struggling with bad code?
Most of you know the situation. You start on a new project inheriting shitloads of legacy code. Not only are you struggling getting an overview but also you are faced with enormous side effects when changing the tiniest thing.
This surely is the worst ever project!
Have you ever felt the urge to make this public just so other like minded developers can sympathise?
What got me started with this post is a video by Robert C. Martin (Uncle Bob) about bad code.
His example is truly aweful! But he took care to disguise it so it can not be tracked down to whatever company owns this code which would be fatal for him as the company might would probably sue him then.
Also just recently I had to say farewell to an ex-colleague of mine who has left the comapny because he felt completely entangled in legacy code with no chance to advance his skills. He told me he often thought about showing the worst examples to the outside world as a means to cry out.
I do have to say I often felt the same and during my last few years each job introduced me to at least one project that instantly made it to the top of my list of worst projects ever convincing me that it couldn’t get any worse than this.
A website that I found very early on and that now entertains me for ovwer half a decade now is The daily WTF.
So far I didn’t publish anything there. Instead I blogged right here on test.ical.ly with great caution not to tell names or be too obvious.
How do you handle this?