General Updates
So I’ve done very little writing on here lately, and lots has happened. There have been plenty of important events in international relations in the past month, from the collapse of the Doha round to the Russian intervention in Georgia. My (few) readers can expect more posts on topics like these in the future.
In personal news, my girlfriend and I are getting ready to move to Korea for a year. We’ve signed a contract with EPIK, and will be teaching English in Korean public schools for the next year. Expect updates and photos about this adventure.
I’m looking forward to a sweet Korean internet connection; the last few weeks at home (and on dial-up) have been frustrating. I think we’ll be pretty grateful for the internet over there. Given that we don’t speak a word of Korean, and we’ll likely be in a small town somewhere in Gangwon-do, I expect we’ll be spending lots of time with our computers. I’ll be using it as an opportunity to make this blog a higher priority. I miss writing, and even this informal BS is enjoyable.
Check back soon for more info, and if you’re privileged enough to have my Skype info, please give me a call now and then.
Flowchart master
The title of this post refers to me. That’s right, I am the flowchart master.
Maybe I’ll back up a bit. I’ve mentioned that I’m developing a training program for new tech support consultants at my new job. Last week (my first week on the job), I made flowcharts. Sounds exciting, doesn’t it? A number of people said that new consultants were struggling with some of the troubleshooting required by the job. It often requires following a process through several steps, and some issues can be a bit confusing. Here’s an example:
A user calls in because they have no network connection. First you have to verify that they have a working network adapter on the computer. Then (hopefully) you can check the IP address. If they get a 192.x.x.x IP, they either have a static IP set, or they’re connected to a router, or some asshat on the network hooked up his router wrong and it’s causing a rogue DHCP server. If they get a 35.15.x.x, they haven’t registered with MSU’s DHCP server yet. It can be confusing to keep track of all this, especially over the phone.
So in week one, I made a few flowcharts in M$ Visio for these types of issues. Pretty boring.
The job is starting to shape up, though. Today I made a couple sample screencasts — videos of the computer screen in action, with me narrating. I think these will be the easiest way to train new hires on some of our software. We use a handful of tools to look up user info, modem status, etc,; timesheets and work schedules are done through web apps as well. My screencasts should get the newbies up and running more quickly.
I think I’ll have a lot of latitude with this training program. It seems like I’ll be making a lot of decisions (or at least contributing), and hopefully I’ll get to actually finish this project. Sorry for the long post, but I figure my many readers deserve to know what I’m doing, right?
