Tonight was my greatest achievement in… well, a while. I worked most of the week on a 30 minute presentation for VSTE’s VirtualVA2013 because I’m that kind of person. Not an overachiever, but a non-talker… an introvert… an internal processor. And then there’s the fact that I can’t pronounce words like “inquiry” and “peripheral” thanks to my Cumberland County slur.
I talked about the importance of third spaces and how they’re vital to the cross-pollination of ideas and the nurturing of the adjacent possible. I talked about the Academic Commons that will open in 2013. I talked about makerspaces. I don’t think I sounded like a lunatic. I think I made sense. I think the presentation went ok. I’m really excited about getting more involved with VSTE. But what I’m really proud of is solving the gigantic Java tech issue I experienced all by myself.
The brief timeline of events: (1) Java wouldn’t launch when I tried to get into the Blackboard Elluminate room. (2) I think maybe it’s because I’m trying to log in too early. (3) That’s not the case. (4) I think, “Well, it worked fine Tuesday. (4a.) Check Blackboard Elluminate support page and see this:
Announcement: Thursday, January 31, 2013 – Some Mac OS users are unable to run Java. This issue will prevent users from opening any Java based application including Blackboard Collaborate Web Conferencing, Elluminate Live! 10, SAS, Blackboard Collaborate Voice Authoring, and Wimba Classroom. We are investigating alternative options and will provide update in this area as soon as possible. Click here for more information.
(5) I try to update Java (6) Software update wants to connect to school’s software server. I’m not at school. (7) Being mild panic attack. (8) I vaguely remember logging into the school’s server via a VPN a few years ago. Surprisingly, I still remember how to do it. (9) Update Java. (10) Still no go. (11) Fine. I’ll do this workaround, which involves the terminal and sudo and warnings that you had better be sure about what you’re doing:
WARNING: Improper use of the sudo command could lead to data loss or the deletion of important system files. Please double-check your typing when using sudo.
But what the hey. Java was screwed anyway. I had nothing to lose but the connections with other educators and the time I spent preparing.
And there we go. It worked.
Here’s the thing though: If it weren’t for my failed attempts at C programming and Unix school and a Linux class, I don’t know if I would’ve been comfortable futzing about in the terminal. If it weren’t for past experiences, I probably wouldn’t have known to access the Collegiate server through the VPN. Even though updating Java didn’t work, it was a possible solution.
What am I getting at? I think I did some creative thinking under a deadline, and I’m pretty pleased with how things turned out.
And this brings me to my Maker Manifesto that I did for senior seminar.
Figuring out how things work–even if it’s just trivial figuring–is empowering. Having some idea–just a basic idea–of how things work or talk goes a long way in finding a solution. That’s one reason why this maker movement is so appealing. To make something, you need to know about all of its parts. You need to know how it fits together. Crawl under your house and spend an afternoon rerouting water lines and you’ll really develop an appreciation for indoor plumbing. You’ll also develop an understanding for that system. Understanding the system leads to better hacks, better solutions, and maybe better systems.