A Long, Buggy Night
It was about 4:00 AM. The office was dark. I was exhausted.
For the umpteenth time, I walked back into the office of the lead architect to demo the web app that was due to the customer at 8:00 AM that morning. Again, he managed to break it.
Dejected and frustrated, I went back to my cube. Over the next two hours, I managed to ferret out the rest of the bugs and, thanks to the architect who stuck with me the entire night, the product was delivered on time.
I will never forget that very long night many years ago, because from that experience, I learned my most profound and important lesson about technology.
The Message
The next day, I met with the lead developer, who at the time was a sort of mentor to me, a newbie programmer analyst. An analyst, who, without a classic background in computer science, was trying to make the switch from client account management into development.
About the program I had wrestled with for many weeks, he said:
“It’s just doing what you told it to do.”
As a young developer, I of course didn’t comprehend the profoundness of what he was telling me. I just wanted the program to work, per the requirements. I told it to do X, and it’s doing Y, and if it does not starting doing X soon, I’m going to blow this incredible opportunity.
The next day, I was debugging yet another program when hit me like a ton of bricks: I’m the one causing the problem. The program is broken because of me – it’s not the program’s fault. I’m projecting what I think the program should do, but I’m not communicating correctly what I want it to do. It’s only doing what I tell it to do.
For some, grasping this seemingly “duh” concept comes very easily. Others don’t care. But for me, getting my head around this fact fundamentally changed the way I look at technology. I was now the solution (or the problem), rather than the technology running the show.
From Emotional, to Rationale
I call this phenomenon “technology projection” – when something goes bad, the technology is to blame. Technology projection replaces logic with emotion, which in today’s fast paced, no margin-for-error business environment, can be incredibility destructive both inside and outside IT.
Unfortunately, technology projection is still alive and well today, and it takes strong, seasoned teams to overcome it. Teams that are good at separating themselves from the problem, able managers who understand how to recognize it and educate the business about it, and supportive executive management that champions the time, cost and effort of maintaining a mature technology function.
Note: I do still curse at my ERP system from time to time, but these days, I apologize.
—
Image courtesy Flickr user Anthony Easton

Posted by Stanton Jones 

