Getting technical

While others see me as tech savvy, I know that I’m not. What I am is patient, and willing to experiment. That’s different than savvy. Why do I say this? Because I struggle. I get lost, I make mistakes. I screw up. A lot!

Whenever I’m doing something technical, I have to go painfully slow, or I have to take one step forward and two steps back. This isn’t about me trying to be humble and under-representing my skills, it’s a reality that I’ve come to accept. This is most evident when I try something new. I’m the guy that misses a step, or tries something that I’m too novice to try.

I can remember when I first tried blogging. I’d play with the HTML and quite literally break my blog. Then I’d spend a couple hours on the back end, going way over my head to try to get something besides an error page to show up. But I figured it out. I muddled through.

Sometimes these trail and error escapades left me pulling my hair out, other times laughing at myself, and sometimes feeling like I wanted to cry (especially if my mistakes cost me money unnecessarily). But I try, and I try, and I try. And unlike the song, I find that my attempts create amazing opportunities to learn… and despite the frustration, my attempts at bring more technical than I am are very satisfying.

Your chance to share:

2 thoughts on “Getting technical

    1. David Truss

      Your links were a trip down memory lane. At first I thought, ‘Oh no, I already wrote about this’, which is a thing that can easily happen when you blog every day. But it’s additive, I think (I hope), and not just a repeat. Effort and attitude, yes. The interesting thing is that attitude makes the effort easier or harder, without the actual work changing… which might be another post.

Comments are closed.