That is not something I would have expected when I first decided to become a teacher.
What I should have expected, though, is becoming the resident tech guy by default just by being competent with technology and knowing how to problem solve.
---
"To truly live, one must first be born." ~ Evan [aX]
Paper Mario Social: The Safe Haven of GameFAQs. (Board 2000083)
Photoshop was something I picked up while I was in my last job when I realized that I wanted/needed more universally applicable skills in case that job went sideways. Luckily I had foresight on that front, I guess. I'm also one of the default tech guys in my office, if only because I'm more accessible than having to call our actual department IT guys since they're stationed in another building on campus. But it's more because I'm one of two people in our office who does know how to computer problem solve.
And by problem solve I mean "teach my supervisor how to do basic tasks a lot" and on one occasion "help her log into Pinterest." But she's extremely professional in every other realm, so I don't mind that much.
---
http://img.photobucket.com/albums/v129/ukealii50/kylo.jpg - Thanks uke!
http://img193.imageshack.us/img193/829/07kyloforce.png - Thanks Diyosa!
I do a lot of research-related programming. And I have no complaints. It kind of combines the best parts of professional and amateur programming: I get to feel like I'm writing something actually useful, and yet I don't have a pointy-haired boss telling me to use Ruby on Rails because it's trendy. I can also to make all my software free, so I get to enjoy that warm and fuzzy feeling when my code gets merged into a big important project.
---
One man's converging evidence is another man's pilpul.
I do precisely none, but I do some technical writing and have even made a presentation or two and done some public speaking. The public speaking was the most surprising part for me.