Techy Vs. Non-Techy

May 14th, 2008

Experimentation.  I think that is the most significant difference between a “techy” and a “non-techy”.

When confronted with new technology, often we techies haven’t a clue what to do before we dig in.  So, we go slow, poke around, and generally try to get a feel for what is going on.  Then, we start trying things that seem innocous and keep moving up until it starts to make sense or we run out of options.  Luckily, 9 times out of 10, it starts making sense.  Technology is at its heart, always logical.  The trick is to figure out the logic of that system.
Non-techies are reluctant to log in and poke around until they feel that they understand it.  Often, they are afraid that they will break something, look stupid, or generally be “wrong”.  I understand these feelings.  In my past I have certainly done them all with aplomb.   But, this foibles were rarely permanent, costly or scarring so I haven’t let it stop me.

Experimentation is important because without it, understanding is hard.  You need to see the interface, read the lingo, watch the interactions to make sense out of a system’s logic.   Once you begin, then it starts to become clear bit by bit and piece by piece.

Of course, once you understand a little, then the earnest questions begin.  But, then training will be most effective.  Now, you have a “place” for the data, a paradigm to fit the instructions into, and more specific questions.  It becomes less “I don’t get it” and more “What happens if I click ‘edit’?”

What is the best way to experiment? Start with files that you can destroy (samples, copies, etc…).  Then, click around and see how far you get.  Try to follow the paths that make sense and find familiar paths (like file -> save).  I bet many non-techies would find out they have a little bit of techy in them after all.