Weak Interface
When the computer people meet the other side

One complication of being in an industry that is not well understood is explaining to those outside the industry what you do. Meeting new people gets a little complicated when you hear the simple ‘get-to-know-you’ question,
“So what do you do?”
I don’t like to say, “I work in computers.” That answer covers everything from ‘design national networks that millions rely on’ to ‘working IT at a small store’. Vastly different ends to the spectrum.

I have a friend, ‘Smiles’, who works in the search engine optimization business (think ‘Google’ if you don’t know). When she starts to explain her specific job, eyes glaze over as anyone who needs the explanation gets lost fast.
Another friend, ‘Beck’, is a programmer and he just tells his family he’s like a cable repairman. Not even close to what he does but it is a platitude that let’s him not have to try to explain writing software to people who don’t even understand what a computer is.

The best way I’ve found to explain my job is through analogy and I encourage anyone in the industry to create some that work for them. For example when I was working on guidance systems I merely said,
“I help the machine understand what it sees. Like explaining road signs to a new driver.”
not my favorite analogy but it allows for a very general idea of my job without having to explain the history of computers to someone. Here’s the problem with this solution. Since you don’t get very detailed with the analogy it can give the illusion that your job is easy. People tend to forget that it takes years of experience and a lot of knowledge to be able to do even “simple” programs on the computer. Please if you hear anyone in the computer industry describe their job in simple terms or via an analogy do not assume that the job is ACTUALLY simple.

The best advice I can give: if you’d like to understand the computer industry better would be to go to your local library and ask for some intro books to read. Then sit down and read them. Then sit at a computer and use that knowledge a little.

That’s all for now folks!
Take care.

   Most programmers have had the experience of having a client, be it their manager or paying customer, ask for a change outside of what they originally designed before the system development started.  Of course it is often thought of as a “simple” change.  It usually starts at a demonstration or meeting with a phrase like,

    “Can’t you make it do this thing I just thought of?”

this is like asking a builder to add another bedroom after the walls are framed out.  Not always simple and in no way cheap.  Sometimes it is and sometimes not. 

   From my own experience I’ve seen both.  At a demo for a large project the lead of the largest team was presenting as he knew the system best.  At various points in the demo he was asked to add or change a feature.  He deferred all the requests to the lead of the area concerned. The problem was that not all changes are created equal.   The situation rises where the guy next to you has been asked to move a button and they say

    “No problem”

but you get asked to ADD a button that will mean new modules and algorithms must be written to perform some feat which may mean an additional 40 hours of work.  When you say that it will require a week’s effort you look like you’re dragging your feet.  I was not asked to change any of my software but I saw this happen to one friend of mine.  The request came from a supervisor who insisted it shouldn’t take that long.  This is the Weak Interface in action.  The knowledgeable programmer has been asked for something and responded with his honest assessment, while the supervisor, who has never been a programmer, makes assumptions that he thinks should override the opinion of a professional. 

   You can imagine how it ended but if you need closure let’s just say it was not resolved without casualties.

My advice for supervisors: listen to the guy you hired to do the job.  If you don’t trust him why is he on your payroll?

My advice for programmers: hope you never get into this situation or get on a new project with supervisors who know enough to trust your opinion.