Categories
Work in the 21st

Why I stopped wanting to be the tech guy

1 min read

When I was a kid I wanted to be “the tech guy”. You know the one. The wizard that everyone goes to when they have a problem.  The guy with all the answers.  Mr. Fixit.  I thought it’d be great to be able to help people stay up and running when their computers went down. To be problem solving every day.

Fast forward a decade or two.  My mind has changed.  I don’t want to be the tech guy anymore.  I could tell you that it’s because problem solving all day every day is hard.  Maybe it’s because what used to seem interesting quickly became mundane.  But I have another theory.

I don’t think there should be a tech guy anymore.  When I first got into it, computers were simpler.  Less reliant on the internet.  Less applications.  Less complex.

I don’t believe companies should have a tech guy because I think everyone should be the tech guy.  The ability to solve your own problems, to find new and innovative ways to do things. These can’t be delegated to a single individual or department.  That creates a bottleneck.

Any company that wants to thrive in the future needs to have a full compliment of tech guys and gals on their team.  Everyone should be cross trained in basic fundamentals of networking, problem solving, logic, and troubleshooting.

The benefits extends far past your computer.


Understanding networking allows you to understand how every computer, phone, and person is connected to each other.

Problem solving is an art form that transforms problems into opportunities.

Logic is the fundamental building block of good decisions.

Troubleshooting a computer is no different from troubleshooting a person, a team, or a customer.

Leave a Reply

Your email address will not be published. Required fields are marked *