Being technically literate can be a strength and a burden at times. I know the ins and outs of computers, I know how to handle a SmartBoard, and I know how to troubleshoot problems involving audio and visual equipment. Basically, knowing how to troubleshoot is the crux of the issue; you immediately become an expert in the field of technology, just from knowing how to diagnose a problem and potentially address it using the computer’s intricate menu systems. You become your coworkers’ favorite technical friend, even when the school has someone else for this purpose. Resulting from this, I’ve been called into classrooms on a few different occasions to help people figure out their technical problems. Whether it’s a broken speaker, a phone that won’t upload pictures, or anything else like that, it’s my job to help out whenever I can. So there’s a bit of anxiety associated with this; I never know when I’ll be called into someone’s room to work on something with them.
I used to own a camera, in fact I still do, but I haven’t used it in ages. I’m not sure I would know what to do when fixing one of those, to be honest. But when it comes to computers, I’m your guy. I’m not enough of an expert to join a Nerds2Go group, but I know my way around the technology. I earned a few brownie points with students when I told them I’ve built a computer before, and they seem to respect that I know more about these things than most other adults in the building. Just knowing that I have a computer at home that I use in my spare time is probably enough to figure out what’s going on when there’s a problem brewing. This is what it’s like to be technically literate.