August 14, 2005

It's Not the Size of The Tool...

This post at Business Pundit put me in mind of an experience early in my career as a designer. Actually, it was this specific paragraph.

I'm reminded of a story an engineer friend told me years ago. When the first hardware description programming language came out, it made circuit design much much easier. How did his boss embrace the new tools? By drawing out circuits the old way and having one of the young guys code them into the new tools. Why not learn the new tools? Fear. Apathy. Or maybe because we see our value in knowing how to do things, when really our value should be tied up in learning how to do new things and apply new knowledge.
My first boss was something of an old school type - although he is my age. He berated me constantly to show him sketches of my ideas before I sat down and did anything on the computer. He wanted to see the plot without the special effects.

The problem for me was, and is, that I cannot draw well at all. I can barely manage a decent stick figure. So my solution was to shut myself in my office, work out my ideas on the computer, then trace them. I'd present these “drawings” to him. He would make his comments and I go back to my desk to start “working them up.” It worked out well. He was happy that I took the time to work out ideas by hand, and impressed as hell with how fast I could go from “sketch” to finished layout.

Then, of course, I got caught.

He walked into my office while I working away on one of my “sketches.” There were two completed “sketches” with their originals on the desk. For a brief moment I thought I was going to be out of a job. Either that or he was going to destroy the computer and he gestured at it wildly why exclaiming that the answer to the design problem is not in that damn box.

At which point I picked up the box of Sharpies on my desk and threw it to him and calmly replied, “it's not in this box either.” I followed that by pointing out that the pen and the computer were both tools. I challenged him that even when he was sketching out an idea he was probably thinking on some level about how it could be done on the computer. He couldn't deny it.

I never had to present “sketches” again.

Posted by: Stephen Macklin at 05:24 AM | Comments (2) | Add Comment


1 I'm imagining you printing out your design and tracing it on a blank sheet of paper, preparing to show the boss your latest "sketch". That's just weird. Hillarious, but weird.

Posted by: Tuning Spork at August 14, 2005 06:01 AM (Sm79t)

2 In one Air Force assignment we had to write "pseudo-code" for the boss before we could actually write a program. When he got my first "pseudo-code" he went ballistic because it consisted of whatever got the idea across best. A few lines of BASIC followed by a scrap of flowchart followed by a written paragraph and so on and so on. There was no structure at all to the method, but it adaquately described the steps of the program that needed to be coded.

After getting chewed out, from then on I just wrote the program first, made a copy and removed the command lines to make it "pseudo-code". That made him happy.

Posted by: Ted at August 15, 2005 06:51 AM (blNMI)

Hide Comments | Add Comment






24kb generated in 0.0344 seconds; 40 queries returned 179 records.
Powered by Minx 1.1.4-pink.