It’s nice that geeks are cool now. Now there are a lot of people who say they’re hardcore. Here’s some of them:
These stereotypes are not who I’m going to be talking about, though I do have some guilty pleasures of a few of those portrayed above. I’m going to talk about me and my kind. The high end technology workers. People who were geeks before the big money and the sexy arrived to geekland.
The tech industry, and information security especially, is rarely understood by outsiders. I was reminded of this recently when I came to realize that none of my non-hardcore-geek friends, all of my family, and also many different-interested nerds didn’t get what I do.
I thought that a bit of my history and example would be helpful by way of explanation.
Titles I’ve had in the past has included:
- System Administrator
- Network Operations
- Information Technology Manager
- Various consulting titles in Systems Management, Information Security, Risk Management and others
- Chief Information Officer
- Board membership of various associations and businesses here and there
- Speaker and presenter
So what do these things mean? Well I guess that’s the problem. In themselves, they all basically mean the same thing but the responsibilities are a bit different. Really what people like me do is something of a business to geekland ambassador/translator, technology manager, risk manager, and court wizard.
We are the experts that you need to make sure the company, people, or organization is correctly driving technology. Without involving someone like us from time to time (at a minimum), you risk running your ship aground on rocks that you didn’t know were there.
People like us can do things like telling organizations:
- Where they’re spending too much
- Where they’re not spending enough
- What risks they haven’t identified that threaten damage to their business or brand
- How to manage what they have better and cheaper
- How to break huge systematic/complicated problems into workable chunks
I’ve spent years doing the unlikely for employers who often thought what I was doing was impossible and many of the rest didn’t understand what I was up to at all. I’ve made jokes about operationalizing the black magic that holds the internet together, herding cats, and the usual fairly weak geek cliches for our industry.
So what is this job really? It’s a layer cake.
It is a stack of skills and concepts that build and commingle with each other. A deep understanding of how a large variety of technologies work and interact.
The complexity involved is what makes doing this job well difficult. There are usually hundreds (or many thousands) of ways to solve the problems that we work with, but usually only a few that are the best. The best being the greatest bang-for-buck, cost savings in efficiency and productivity, risk reduction, or a combination of these.
This is not something you can read a book about, go to a community college to be prepared for, or complete a training course in and expect to be equipped to handle. It is compounded mastery of difficult and frequently changing subject matter.
Qualities that everyone who is good in this field have includes:
- That they never stop learning
- They want to know how things work
- They crave solving problems
- They enjoy a challenge
It isn’t for everyone.