Forums
We received a lot of entries that were pretty great, but we only had so many prizes to give out. Here are some honorable mentions that we still want to share.
Yesno was the only entry written in Haskell. Language choice itself isn’t interesting, but if you’ve ever touched Haskell, you wouldn’t expect to see code like this:
Picking the Grand Prize winner for the Second Olympiad of Misguided Geeks at The Daily WTF was truly a monumental challenge. The grand prize winner needed to embody the most all-around WTF solution possible. There were a plenty of great (terrible) entries but were looking for that one special entry that hurt our souls and ate our brains. Something that made us exclaim "WTF?!"
In the end, it came down to two submissions. Both are great examples of bad development practices, but in the end one outshone the other as worse than failure. So, before we get to the grand prize, let's take a look at the code which almost won.
Programming languages make it super easy to pick a random number. A call to a built-in 'generate random number' function returns some float value between 0 and 1.0 and really the only heavy lifting for the developer is to turn that into a bigger number, a boolean (yes/no), or whatever. Ta-da. It does exactly as it says on the tin.
So, naturally, in a contest like ours, if a developer can think outside of the box and deliver a truly novel way of choosing a random result, he or she deserves a tip of the hat, or as we like to call it, the “Casino Royale, with Cheese” award.
When we first started the OMGWTF2 contest, one thing that we hoped to make clear in our FAQ was that we really only wanted submitters to do his or her best on their entry's UI. After all, this is a coding competition not an art contest.
However, if you were a special developer who could weave together a abomination of a solution and make it look extra pretty, well, we felt that combination deserved special recognition and thus, the "Lipstick on a Pig" prize was born. The recipient? Randolpho and his entry: "Ask Threepio"
While going through entries for OMGWTF2, one question often crept in our discussions “What would it be like to have to maintain this code?”
Some entries tried to enter our nightmares based on their otherworldly variable and function names, others revealed themselves as colossal-sized horrors with regards to the sheer size of the code base. However, one entry stood out among all the others - Oxin’s entry written in HTML and "Diarescript".
It’s that time- time to review the results from the OMGWTF2 programming contest.
Jul 13
var procs = from proc in Process.GetProcesses()
where proc.ProcessName == "java"
select proc;
foreach (var proc in procs)
{
proc.Kill();
}
When a new company is formed, it's usually just the owner, possibly some partners, and a small staff. As they figure out how the business is to be run, they come up with their own ways of doing things. Over time, the staff grows, and more rules are created about how this or that is to be done. Eventually, it reaches critical mass, and all of these rules get quantified into written guidelines. Sometimes this can be a good thing. For example, coding style guidelines, if done correctly, can be a good thing.
Unfortunately, beyond a certain point, the company becomes bureaucratic, and the folks making the rules tend to be insulated from the bigger picture. People start clarifying rules to add finer grained detail. To the point of lunacy. You get stuff like instructions on whether of not to put a space before a semicolon; in which corner of the page a staple should be used, and at what angle it should be to the page, or how many sheets of TP to use for #1 vs. #2, and whether you should choose one ply or two ply. The rules start to resemble a mindless automaton, blindly forging ahead, without thought, sensibility or sentience. It's enough to suck the life out of any well-meaning effort.
It was spring (or autumn, if you live south of the equator). A time when everyone's heart is a little bit lighter. When the layers of clothing are worn just a bit looser. When even the infirmed have a spring (or autumn) in their step.
Everyone except for Tim.
Keith received a ticket regarding a very large, very important, and very complex application, written in Perl. Keith’s first step was to scan the file for variables, so he could get a better sense of things he should look out for.
He found this:
Les got an unexpected promotion to head developer, when his cranky old micromanaging boss Frank tendered his resignation one Monday. Frank knew his stuff, but couldn’t silence a constant whine over any grievance, no matter how slight. It would be a relief to not have to listen to him complain about everyone any more, especially his complaints about Phil, the Vice President.
Frank’s chair had been empty for mere seconds when Phil stepped in to Les’ office with a performance issue in production. Phil explained that the company’s bread-and-butter website was crawling at a snail’s pace. The site had only been rolled out to half of their contracted users, and Phil was worried about scaling. “I need you to look into this right away. This is a great opportunity for you to show me how you can handle big responsibilities, Les!”
In the beginning, The Founder had a vision. He hired Manoj P. to develop a shiny brand new system that would embody The Founder's vision. He would have the freedom to design and build it any way he wanted. He could choose his own languages, tools and methodologies. The Founder laid out his vision and Manoj started typing. Thus was born Team WTF at what would become WTF-Inc.
Over the next few years, Manoj would encourage The Founder to hire his comrades to help. And help they did; they copied and pasted each other's code hither and yon, over and over. Features were added. The code and functionality grew at an astounding rate. Unfortunately, none of them had ever heard of the concepts of scalability, threading or aging off data. As features and customers were added, the database grew geometrically. Along with the hardware requirements to support it. And the cost. It was at this point that The Founder had an epiphany; let's hire someone who has more than 2 years of experience to help sort out the mess. Enter Snoofle.
Nate worked on software that communicated with onboard computers for large machinery and industrial vehicles. Two releases a year made for a tight development schedule, but the fast turnaround created plenty of variety. With the next release cycle, he’d be taking the lead on the highest-priority feature: an Engine Theft Deterrent (ETD) system, something unprecedented but interesting.
“How ’bout we just hire a guy to stand by the engine with a gun?” Nate asked.
