Define Failure As Success
by in Feature Articles on 2006-09-28
Sorry everyone, I don't have a story of massive failure to share with you today. Instead I thought it'd be fun to share this simple story of success -- or at least, success as defined by a vendor at Jamie's company.
A few months back, Jamie's company ran into a Serious Production Issue with their system. I'm sure you're all familiar with the SPI routine: the overhead lights dim; metal sheaths slam down, covering the windows; red SPI lights are activated; an ominous voice repeats "serious production issue" over the PA system; and a special forces team is assembled to solve the problem. At least, that's my company's procedure. Well, with the exception of the PA voice. We hired Majel Barrett (voice of Star Trek's onboard computers) for all of our automated announcements.
It was to be the perfect system: requested by an IT-friendly internal client, managed by a competent project manager, described by insightful business analysts, designed by an experienced architect, built by intelligent programmers, and perfected by thorough testers. Its goal was hefty but noble: replace the current manual billing system with a fully automated process that tracks jobs, hours, accounting, and payroll. It was to save employees across the organization a lot of time and save the company a lot of money by bringing payroll processing in-house. But alas, it was confronted by an obstacle it just could not overcome: the Chief Technology Officer.
Kristopher has the pleasure of working with Robert, The Infallible Programmer. Robert (his earthly name) is actually one of the world's two programmers who have never coded a single bug. The other bug-free programmer, though not infallible, is the guy who writes all of those "Hello World" examples.
We were outside the main gate, waiting for security to come down and escort us to the deepest sanctums of the complex. We had been waiting for nearly two hours. At last, two guards came for us, their pace a slouch more than a march.
Back in the year 2000, Frank slaved away as a peon for fairly large consulting organization. Though his title technically was "Programmer", he did very little actual programming. His job mostly consisted of creating test data scripts, writing technical documentation, and analyzing code to see what the actual programmers might need to change. It wasn't very exciting work, but having experience at that particular company provided an excellent ROR (Return On Resume).