Weekly Musings 138
Welcome to this edition of Weekly Musings, where each Wednesday I share some thoughts about what's caught my interest in the last seven days.
What you're about to read has a slightly different shape from what I normally send your way every seven days. For whatever reason, the ideas that make up this edition of the letter rigidly refused to coalesce into flowing paragraphs. Instead, they remained frozen as points — more, I hope, thinking points rather than mere talking points. So, instead of hammering away at something that wouldn't bend to my will, I went with the form of what was on the (digital) page.
Regardless of whether this format works or not, thank you for putting up with my (inadvertently) indulging in a little experimentation.
With that out of the way, let's get to this week's musing.
On Being Tech Savvy
Savvy: having or showing perception, comprehension, or shrewdness especially in practical matters — Merriam-Webster Dictionary
The term tech savvy is bandied about a lot. But what does the phrase being tech savvy actually mean? What does being tech savvy actually entail?
Many people would say that being tech savvy means being able to bend technology to your will, almost effortlessly. That the tech savvy are like polyglots when it comes to technology, able to easily and fluently move between technologies.
I don't see there being any universal definition of the term. It has different meanings to different people. Those meanings are based on what they need to do, not what others think they should know.
Being able to use an app or a search engine or quickly message or set up and use a social media profile doesn't really make you tech savvy. Those are mechanical tasks in which can become proficient with repetition.
On other hand, having deep technical knowledge, being able to code, being able to host your own infrastructure is definitely being tech savvy. But it's a level of tech savviness that most don't need.
Being tech savvy isn't (always) a matter of embracing your inner geek. Assuming that you have one.
Being tech savvy means embracing technology to the level that you need, not at which others think you need. You definitely don't need the chops of a coder or a system administrator or a DevOps person to use technology. But you should know the basics, how to do what you need to get done in the most efficient manner. That could be sending an email, writing a report, taking notes, publishing a blog post, or editing an photo.
Being tech savvy could mean having a wide and yet shallow base of knowledge, and being able to generalize that knowledge. To apply what you know about one technology or piece of software to something else. More importantly, it's being able to adapt to the quirks (real or imagined) of what you are or find yourself using at any time.
Focus on skills, not software.
My wife's laptop is an old MacBook Air that I bought from a previous employer for about $75. I use Linux. On those rare occasions that I have to use her fruit machine, I need remember the different shortcuts that are predicated upon the differences between the Ctrl and Cmd keys.
To be honest, I'm on fence about whether knowing bunch of tips and tricks, no matter how useful or how nifty, makes you tech savvy.
A while back, I introduced a coworker to a useful shortcut that works across just about every application we use at The Day JobTM: with CTRL-K (which quickly inserts a hyperlink). It was as if she unlocked a superpower by learning that shortcut. When she told her partner, a software developer, about it he, too, was surprised. It turns out that he didn't know about the shortcut, either. Although they didn't know something that seems so basic, that doesn't mean the two of them aren't tech savvy.
On the other hand, being tech savvy could mean specializing. It could mean having a very narrow focus — graphics work, word processing, using productivity apps. It could mean knowing the ins and out of those tools, being able to squeeze as much out of them as possible. Being tech savvy also involves understanding the limitations of those tools and what you can do to get around those limitations if and when you need to.
Over the years, my view of being tech savvy has evolved beyond the idea of merely knowing how to use and adapt to technology. That view is also wrapped up in knowing how to protect yourself in the digital world. About being able to spot phishing emails or texts. About knowing how to block or minimize online tracking. About being wary of public wifi. About understanding how to spot a scam or a suspicious URL.
Being tech savvy definitely involves awareness, not just blind clicking or assuming that all is well. Most of time, all is well. But to be safe, to be tech savvy, you need to know the signs of those times when things aren't well or the signs which are pointing in that direction.
Being tech savvy means knowing how to secure your online accounts, how to use multi-factor authentication, when and where to use password managers, how to block email addresses and phone numbers, how to turn off tracking on web and on mobile devices. You don't need to be a security professional or a card-carrying paranoid to understand all of that and to do all of that. You only need to be, as I a pointed out a moment ago, aware.
That awareness extends to understanding that the measures you take to protect yourself might not always be enough. That tech giants still track you, even if stop using or don't use their services. That you might need one more layers of defense to protect yourself from those online who don't have your best interests at heart.
It also involves educating yourself about technology, specifically the aspects of technology that are important to you. Do that by reading, taking courses, asking questions. And remember what you've learned — keeping a notebook or creating a simple personal knowledge base or digital garden can go a long way towards doing that.
For most of us, being tech savvy doesn't mean being a ninja or an expert or a guru. You only need to know what you need, what you use, and to be able to adapt.
I'll close with this thought, which comes from a a survey of the skills of judo champions. A conclusion that applies not only to judo, but also to the way in which we use technology:
You have to use the skills that work best for you. You have to stick to what works and practice your skills until they become automatic responses.
Something to ponder.