Recent Feature Articles

Oct 2013

The Call of WTF

by in Feature Articles on

From the archived blog of Paul, recovered from a USB stick found beneath the raised tiles of a decommissioned server room, long forgotten.

The most merciful thing in the world, I think, is the inability of the human mind to correlate all its contents. But what of these modern times of connectivity, with the ease of the piecing together of disassociated knowledge? Can any information be safely sequestered away-- fragmented and separated, never to come together and burrow in the minds of men?


The Curse of the Warped Bootstrap

by in Feature Articles on

“Hey Stan, can I use mockingbird?” Andrew asked, leaning into Stan’s cube. He had to do some rigorous performance testing for a customer-reported issue.

Stan gave a start, ripped out his earbuds, and glanced back nervously. “Use sesame.”


The Flux Capacitor

by in Feature Articles on
Google+

After two weeks of vacation, it’s easy to forget the little things. Chad left his ID badge at home. That’s inconvenient in any office, but when you work at a US Naval Base, they take security more seriously. Without his ID badge, the door wasn’t supposed to open.

Chad was a Marine veteran who had become a civilian IT contractor. The enlisted men had a name for this sort of security: “Private Proof ”. A Marine Private might be stymied, but anyone with two brain cells to rub together could bypass it. Chad and his co-workers kept a large “year-planning” calendar on the insecure side. Chad pulled it down off the wall and slid it beneath the door. Waving the calendar around triggered the motion-sensor on the secure side, opening the door.


WTF Inc Epilogue - From the Other Side

by in Feature Articles on

Most folks know that I've spent the last couple of years on Team-WTF in Department-WTF at WTF-Inc. A while back I moved on to BigCo Inc. This place is a huge bureaucracy, but somehow, things manage to get done. As with most places, it has its share of (sometimes epic) WTFs, but those can wait for another day. This time, I got to witness WTF-Inc - from The Other Side.

Due to government regulations, BigCo found itself in need of the sort of services provided by WTF-Inc. Since there are only two companies that provide this type of functionality, and the other company has a long way to go to catch up to WTF-Inc, BigCo didn't have many alternatives, so they decided to check out WTF-Inc. As part of it, someone at BigCo got the idea to search its huge HR database of resumes to see if one of its myriad employees has ever had any association with WTF-Inc. One name popped up.


Authenticated Authentication

by in Feature Articles on

Like a ninja in the night, Hanz M., AKA Hanzo, stalks across Hesse University’s Dresden campus. The go-to man in the IT department, he fixes the messes that others leave behind. This is one of his stories.

"You absolutely must read this," Hanzo’s boss Gertrude said. "This is beyond hilarious."


Hashed Code

by in Feature Articles on

Jan had been tasked with digging into a Java web application exhibiting odd behavior. New users couldn’t create accounts, and existing users sometimes found themselves logged in as other people. Concern about sensitive personal data being exposed to the wrong individuals had raised many corporate hackles, especially within the Legal department. While unresolved, the issue left the company open to litigation.

It was easy to rule out a state management issue. After that, Jan traced a typical login, and noticed something odd. The ID for his test account was 102, a value that came from an autonumbered column in the backend database. However, the application had to pass user data to an external vendor’s iFrame, which had its own mechanism for handling user states. Inside the iFrame, Jan’s ID was 48627.


Advanced Adventures in ActionScript

by in Feature Articles on

"That's a natural twenty," Eric said, leering at his coworkers over his Dungeon Master's screen. "Tim, the kobold decapitates your Elven Ranger." The players groaned, and Tim could only mutter in protest. This was only their first adventure, and his character was already dead? Eric smiled. Tim and Alanna would soon learn that suffering abrupt decaptitation in their weekly Dungeons and Dragons game was much-needed preparation for their new jobs at ScriptCloud.

Eric had only joined the company a few months prior, as their first in-house developer. "They" were ScriptCloud Actionware, a local startup dedicated to reinventing the world of mobile app development. With the hindsight that only half a year of nonsense can bring, glimpses of ScriptCloud's deep-seated WTFitude were there right from the beginning. The interview process had gone slowly, not because of stiff competition or a monolithic HR department, but because ScriptCloud had chosen to post the job opening right before their entire staff went on summer vacation. The staff meeting on Eric's eventual first day was somewhat unnerving, ending as it did with the CEO swearing at the creative director after a twenty-minute argument about a single screen of the app's user interface. The app in question was ScriptCloud's first, a game with about the same complexity as Angry Birds (if none of the success). It was built by Costly European Consultants, and it would be Eric's job to support it.

White Plume Mountain


The Great John

by in Feature Articles on

Nate returned from his weeklong vacation expecting his co-workers to ask him the same boring question, “So how was it?” They never got the chance, because when Nate entered the office, he found half of his coworkers’ cubicles empty. AwesomeWeb was a small web shop which had done well over the years. When Nate went on vacation, they had a small staff of 40. Now, that number was slashed in half.

The survivors explained: “It’s Martia, man! She gutted this place under the guise of ‘cost-cutting’ measures. We’re lucky we survived!”


An IDE Impostor

by in Feature Articles on

Despite having written code for twenty years before he'd even turned thirty, Jim couldn't help feeling like a bit of an impostor. He wasn't suffering from the Capgras delusion, though. He felt the way many of us feel when presented with a new job using new technology - in this case, the .NET framework and C# - that surely he couldn't be good enough at this to keep the job for very long. Surely his peers would find him wanting. While Jim struggled with his own self-worth, one thing he didn't struggle with was choice of IDE: Visual Studio. Intellisense, one-click refactoring, and a host of other features allowed him to fake it till he could make it. As far as Jim could tell, there was no reason to use anything else when developing a .NET solution.

Jim's first assignment was to work on a codebase created by Biff. Biff was a Something-Something-Level 3, so Jim was ready to learn a few new things when he fired up Visual Studio and opened Biff's solution. And learn he did. For example, he learned that VS marks syntax errors with a red, squiggly underline, much like Microsoft Word does with spelling and grammar mistakes. Biff's code lit up like a first-grader's essay about summer vacation, loaded as it was with misspelled identifiers, missing semicolons, and AWOL closing braces. Jim would have wondered if Biff had ever tried to compile the mess, but he was too busy wondering if the senior developer made a habit of typing with his eyes closed, since Visual Studio would have helpfully pointed out these sorts of mistakes as he made them.


A Woman Scorned

by in Feature Articles on

The sound of the phone woke Sergio from a deep sleep.

"We've been hacked. All of our data is gone. I can't believe this is happening"


This Direction, That Direction, Indirection, Indigestion

by in Feature Articles on

Joe G. was working for a financial company that had accumulated more than 20 years' worth of code and cruft. This was compounded by management being convinced that the source of all of their technical problems was IT not caring enough about business interests, rather than two decades of short term thinking. They refused to acknowledge the company's technical debt and believed that IT employees' attitudes were solely responsible for their growing reliability problems.

The code was mostly C++ with some Java mixed in here and there for a few legacy front end applications. Joe was tasked with debugging a problem with one such application called TurdEditor. TurdEditor would receive several parameters from a server at startup, then let users tweak those parameters and click an apply button that ostensibly sent the new parameters back to the server. There was also an environment variable called DOMAIN, that if set would cause all company applications to connect to the test servers instead of those in production.