Recent Feature Articles

Jun 2012

Peachy Real Time

by in Feature Articles on

Back in 1952, the economist William Vickrey proposed a fairly unique solution to New York City’s subway congestion problem: introduce a variable fare that fluctuated during peak times. The idea was that the market powers would help tackle the ever-longer commutes by introducing some simple supply-and-demand principles.

While Vickrey’s subway proposal didn’t gain a lot whole of steam, the congestion pricing concept quickly spread to the public roadways, and eventually became a mainstream economic idea. And in 1995, after technology had finally caught up with theory, California implemented the first such system on Interstate 15. This computer-controlled system of variable pricing has spread to highways across the world, and I’m sure is the exact prior art that IBM “inventors” Christopher James Dawson et al paid homage to when they “invented” and patented this exact system in 2008.


The Program-Generator Program

by in Feature Articles on

When you've been in IT for as long as Pat McGee, you're bound to have survived at least one or two COBOL horror stories. While COBOL is certainly not the worst platform to develop software on (MUMPS will most certainly hold that title through at least our grandchildren’s lifetimes), its extreme verbosity and unique idiosyncrasies make it a challenge for organizations to develop clean, maintainable code.

To COBOL's credit, it was one of the first attempts – actually, it was probably the first attempt – at self-obsolescence. Like today, the programmers of old were far too talented to meddle in trite matters like "business rules." After all, if the managers and analysts could conjure up these business rules, they could certainly write them up in a business-oriented language.  A COmmon Business-Oriented Language, if you will. Of course, we all know how that story ends, and five decades later, COBOL programmers are still paying for that arrogance today.


Server Room Fans and More Server Room Fun

by in Feature Articles on

"It's that time of year again," Robert Rossegger wrote, "you know, when the underpowered air conditioner just can't cope with the non-winter weather? Fortunately, we have a solution for that... and all we need to do is just keep an extra eye on people walking near the (completely ajar) server room door."


Sponsor Appreciation, *bleep*ake mushroom, and More Error'd

by in Feature Articles on

Please take a few moments to check out the great companies that sponsor The Daily WTF.

TDWTF Sponsors

ISVCon Logo   ISVCon - You know how to write software. Selling it is the challenge. That's where ISVCon comes in. Spend three days in Reno, Nevada between July 13-15 getting an intense education in sessions across two tracks on topics including mobile platforms, social network marketing, game development, and cloud computing. Register today!
Joyent Logo   Joyent - This cloud ain't for storing music. Running your apps on Joyent's open-source SmartOS is a different, smarter cloud choice. Automatic and Free 400% vertical scaling, copy-on-write with ZFS, DTrace for killer visibility (heat maps! flamegraphs!) Come check out our stack.
JRebel Logo   JRebel is a JVM-plugin that makes it possible for Java developers to instantly see any code change made to an app without redeploying. JRebel lets you see code changes instantly, reloading classes and resources individually and updating one at a time instead of as a lump application redeploy. Download your FREE Trial Today!
Inedo   ProGet - a NuGet package repository that lets you host and manage your own personal or enterprise-wide NuGet feeds. It's a NuGet Server that's incredibly easy to set-up and install, plus it comes in a Free and Enterprise edition.

And now back to our regularly scheduled program...



Batch of Trouble

by in Feature Articles on

Ben had already been with the University for a few years when Dave joined the team. At some point during the interview process, Dave reached the conclusion that he was here to modernize the team. As a result, he started on a Tuesday, and by Wednesday was telling everyone how he would do their job.

Dave strutted from desk to desk, playacting the highly-paid consultant. In reality, he was here to take over the student enrollment system from Ben. Ben had inherited it from Carl, who had inherited it from Bob. A whole chapter of begats was required to trace the roots of the system. It was mostly implemented in simple batch scripts, and it mostly was driven by simple text or CSV files. It wasn't a terribly pretty system, but it did have a few very important features:

  1. It worked.
  2. It didn't require much maintenance.
  3. It was thoroughly documented and well understood by the support team.