FuglyCode

\fʌ-gli koʊd\ n: How not to code!

Welcome!

2 comments

Welcome to FuglyCode.com, where we study the art of software development and proper code. We currently have two article series on the go, which you can find below:

Its So Fugly...

It's So Fugly...

FuglyCode of the Week
Every Monday at 12pm eastern

Every week, take a look at software code as we study the dos and dont’s of software development.

Latest Article: Multiple Nested If Statements

 

Blog Tools

Blog Tools

Blog Tools Reviews
Every Wednesday at 12pm eastern

Interested in building an online blog?  Join FuglyCode as we review useful blog plugins that you can use on your WordPress blog.

Latest Article:  Blog Widgets, Flexo Archives

A Quick Update

No comments

Hey everybody, I just felt like posting  a quick update.

So first, you’ll notice a new Welcome post on the site’s front page.  The goal of this new post is to help visitors quickly access the site’s latest content.  I expect to replace the post with a full time web page, but until that page is built, keep an eye on the post for any updates.

Also, you may have noticed no articles have been posted for a couple of days now.  Well, I’ve been having some issues with new posts that are waiting to be published.  I hope to resolve these issues soon and begin posting new articles next week.  In the meantime, keep an eye on the site in the event something I resolve the issue this week.

Its So Fugly...

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.

As we begin to ramp up the different articles that will be published on FuglyCode.com, I’m proud to announce our first article series: Blog Tools Review.

Articles of this series will be posted every Wednesday around noon ET and will focus on the different tools, themes and plugins that I commonly use to make my blogs easier to maintain and manage.  It was started on my personal site as a thank you to the open source community responsible for the creation of so many useful and free blogging tools, and will now become a regular part of FuglyCode.com.

If you have any ideas for blog tools that you’d like to see reviewed on FuglyCode.com, feel free to drop us a message using our Contact page.

View the first Blog Tools Review

View all Blog Tools Review articles in the series

Welcome to FuglyCode.com, the site that shows you how to code, by showing you how not to code!

As you can see, our site is quite empty at the moment, and that’s mostly because we just launched.   Rest assured that we are working very hard at preparing some interesting articles about good software practices, common development issues, and, of course, fugly code.

So please bear with us while we get ready.