Its So Fugly...

Do you work with code?  Does the code you work with cause your hand to hit your forehead at least three times a day?  Is the code you work with Fugly?

If you’ve answered yes to any of these questions, then you may have FuglyCode!

Alright, big news on the FuglyCode front, we’re looking to start a new series of articles that will be posted every Monday.  This series will focus on the fugliest code ever created, and how it can, and probably should, be corrected.

Now I’ve worked in software development for a long time, and I’ve seen my share of fugly code.  That being said, I’m also certain that I’m not the only one who’s had to read through, debug and reverse design fugly code.  So I’m looking for examples from you, the coders out there on the internet.

Send us examples and snippets of the most horrendous, scary looking code that you’ve ever had the pleasure (or not) to work with.  Every week, we’ll pick the fugliest of the bunch and try and figure out what went wrong.  We’ll then attempt to demonstrate how it should’ve been coded in the first place.

So if you have fugly code, please submit it using the contact us form.

And be sure to visit us next Monday to see some of the fugliest code out there!

A note about submitting code:

Feel free to submit your code in any coding language.  If possible, try to make your code as readable and as generic as possible.  Do not submit any private, protected or copyrighted code. Remove any personal or sensitive information from the code and rename any variables to generic, non-descriptive names.  The goal here is not to steal code from others, but rather to try and find proper design solutions for poorly written code.