Recent Feature Articles

Nov 2007

Notepad Translation Error

by in Feature Articles on

For several days, Rick was fighting with a third party vendor. Rick's system was supposed to talk to his vendor's system using XML files, but their files were coming back with invalid XML data. Rick complained to a technical contact ("Terry") that the XML they returned was invalid. Terry argued that they were processing the file wrong.

The issue that Rick discovered was that one of the attribute values in the XML file used single quotes instead of double quotes. Terry insisted that the XML file used only double quotes, and made his case by sending over screenshots from XMLSpy and IE, showing that they were indeed double quotes. The screenshot from IE would've looked something like this:


Who Says That Size Matters?

by in Feature Articles on

Not too long ago, The Powers That Be in the emerging eastern-European country of Latveria (as I’ll call it) decided that the time had come for a massive, central monitoring system that would be used to ensure the country’s security. SENTINEL, as the system would be called, involved data exchange between virtually every governmental agency, airports, financial institutions, transit systems, and so forth, all for the purpose of being able to track people and the money they spend. After well over a year of negotiations, The Powers That Be selected Christian B’s company to design SENTINEL’s enterprise architecture.

Over the next year or so, Christian got accustomed to the weekly Latverian commute: wake up at 4:00 AM on Monday, depart from Paris via airplane, arrive in Hassenstadt (Latveria’s capitol) several hours later, work five twelve-to-fifteen hour days, catch a plane back home, and sleep until noon on Saturday. He also got very accustomed with Latverian politics: The Powers That Be, especially those from the Ministry of Defense, were personally involved with almost every decision at every level. And they didn’t take criticism very well. One network engineer was fired on the spot (and some suspect, later executed) for disagreeing with a Latverian director.


The Omni ID

by in Feature Articles on
Please take a quick moment to fill out the WTF Reader Survey!

Joshua had recently started his job at a consulting firm. To get his feet wet, he was added to the team on an application they maintained for the juvenile court system. Fortunately, it had been developed entirely by the company, and everyone Joshua had met at the company seemed to have a good head on their shoulders. Plus it wasn't too big of an application, making it an ideal environment for Joshua to learn.

Joshua's first task was to prepare some reports for the users — an ideal first task for a developer new to a system. Except that it was practically impossible to create the reports they wanted.


Desperate Recruitment

by in Feature Articles on

The Beat on the Street in Peterborough (England) is that Data Interchange is looking to hire Software Developers. And I mean “on the street” quite literally:


Monitoring the Email Monitor

by in Feature Articles on

“Ummm…” the top email in Alex M.’s inbox started, “why did you delete my message about the approval bug? And then delete the message inquiring about the deletion? This issue isn’t going away – please investigate this right away!”

Had this been the first like message Alex had seen, he might have been surprised. But it wasn’t. For the past several weeks, customers, vendors, coworkers, and anyone else who emailed him received some rather interesting status notifications regarding their message. It was seemingly random and consisted of replies like “your message was deleted without being read,” “your meeting request has been declined,” or even “I will be out of office for the rest of the day.”


Leave That One Alone

by in Feature Articles on

"H... hello?" Cid groaned, looking at his clock. It was 4:53 AM.

"Hi, good morning, is this Cid? I hope I'm not waking you up."


It’s How Everyone Builds It

by in Feature Articles on

The transition from computer technician to software developer can be pretty rough. Not only does one have to give up the chic company car (and, of course, all the hot dates it guarantees), but he has to land that rare technician job that has just enough programming work to stretch his job title on a résumé to “programmer.” Garret was lucky enough to find that job at a small computer repair shop we’ll called “AAAA Computers”

Garret’s official title AAAA Computers was “Technical Office Manager,” which came with a job description of “ya know, just do whatever it takes to run the shop ‘n stuff.” Being that Garret was the only employee at that location, this involved everything from fielding phone calls to sweeping the floors at night.


Identity Crisis

by in Feature Articles on

Developers-turned-dev managers often struggle to contain themselves when it comes to bug hunting. After all, they can usually resolve problems faster and better than the coders in their employ. The problem is, no developer wants a boss who takes more time explaining what must be done than it actually takes to do it. That leaves dev managers in the difficult spot of delegating the bug hunt and waiting for results.

As a newly hired development manager of a travel-bookings system, Dan E. found himself in this very situation. Overseeing a crew that was maintaining a fairly large ASP/VBScript codebase, Dan wanted to stay close to the technical details of the project while giving his coders room to do their jobs. So he simply offered some suggestions on what might be causing various error messages to appear.


Doomed from the Start

by in Feature Articles on

When Sergey L. showed up for his first day at his new job, he wasn't really sure what he'd be working on. The hiring manager wasn't very specific. "Database skills are very important," he told Sergey. "You'll be our first real sysadmin maintaining some stuff that a bunch of consultants set up."

Sergey was the first sysadmin that the company had ever hired in its five year history. And no one was really sure what to do with him or where he fit in the environment. As such, he didn't really have a boss. He had a team of bosses. Specifically, everyone in the company.


The Opposite of Backup

by in Feature Articles on

In the early 1980s, George C. was IT support on a team overseeing a large installation of workstations. At the time, this was a pretty novel concept. Several Unix site managers applied to help out but wanted "too much money," according to management. Instead, the IT manager rounded up a bunch of recent college graduates (who were much cheaper). Problem solved.

There were roughly 80 workstations that were being installed, each with two 70MB drives. One drive kept the operating system files (which the users couldn't modify), the other was the user drive for work files. Each system was backed up and updated nightly with a three step process:

  1. Back up all files that have changed on each client's user drive.
  2. Replace old files on each client's system drive.
  3. Delete files that are no longer needed from each client's system drive. For this step it'd just remove any files from the system drive on the client's machine that didn't exist on the server so everyone had a consistent system drive.

That's One Way to Secure It

by in Feature Articles on

Most of the WTFs we get are like light snacks. Some programmer didn't know better, screwed something up, we laugh at it, and hopefully everyone learns something. Other times WTFs are Homerian epics. Today's story is one of those.

Jared L. is our Odysseus in this story. As a fresh college graduate, he landed a good position as a Java webmaster in charge of about 25 web sites. He'd never written a single line of JSP code in his life, but he figured he could pick it up pretty quickly. And during his interview he mentioned that he didn't have any JSP experience, but they made him an offer anyway — it wasn't like he'd lied about his experience level.