Skip to main content

Preparing for 2011-12

I'm preparing for the 2011-12 school year, which this year means learning new software systems, university philosophies, and everything that goes along with any new job in today's connected world. I hadn't really thought about the comparisons until this month, but I am noticing how my issues at work aren't that different from those of my wife at her office.

Group scheduling and management software varies from okay to horrible. I've used several different "groupware" platforms. The new employer uses Novell GroupWise — at least until school starts. Right before school starts the university will be switching to another platform. Not the best of timing, but that's reality in any organization.

The university is also migrating to new learning management software, new Web servers, and a new collaboration platform. What could go wrong?

It's strange how dependent we've become on our networks. My wife and I have struggled with synchronizing calendars between several computers, PDAs, and phones. That's the new normal, apparently.

My wife's employer uses Lotus Notes, an Oracle management system, and a content management system, among other applications that help employees share and plan collaboratively. Of course, there are glitches. Sadly, we accept the problems in every setting because that's the nature of software — at least as we have come to expect it.

I'm not comfortable with shared data; I like my data on my computer. Sharing used to mean sending data on an as-needed basis to people, but now everything seems to be out there on a server somewhere. That means things can go wrong and probably will.

I'm sure the university will transfer data (at least most of it) successfully to new platforms. There will be problems, not the least of which will be training the employees on the new platforms.

It is easy to forget that what we experience on campus is exactly what employees everywhere experience.

I love technology, but it is complex. That's true on campus and everywhere else.

Comments

Popular posts from this blog

MarsEdit and Blogging

MarsEdit (Photo credit: Wikipedia ) Mailing posts to blogs, a practice I adopted in 2005, allows a blogger like me to store copies of draft posts within email. If Blogger , WordPress, or the blogging platform of the moment crashes or for some other reason eats my posts, at least I have the original drafts of most entries. I find having such a nicely organized archive convenient — much easier than remembering to archive posts from Blogger or WordPress to my computer. With this post, I am testing MarsEdit from Red Sweater Software based on recent reviews, including an overview on 9to5Mac . Composing posts an email offers a fast way to prepare draft blogs, but the email does not always work well if you want to include basic formatting, images, and links to online resources. Submitting to Blogger via Apple Mail often produced complex HTML with unnecessary font and paragraph formatting styles. Problems with rich text led me to convert blog entries to plaintext in Apple Mail

Learning to Program

Late last night I installed the update to Apple's OS X programming tool suite, Xcode 4. This summer, in my "free" time I intend to work my way through my old copy of Teach Yourself C and the several Objective-C books I own. While I do play with various languages and tools, from AppleScript to PHP, I've never managed to master Objective-C — which is something I want to do. As I've written several times, knowing simple coding techniques is a practical skill and one that helps learn problem solving strategies. Even my use of AppleScript and Visual Basic for Applications (VBA) on a regular basis helps remind me to tackle problems in distinct steps, with clear objectives from step to step. There are many free programming tools that students should be encouraged to try. On OS X, the first two tools I suggest to non-technical students are Automator and AppleScript. These tools allow you to automate tasks on OS X, similar to the batch files of DOS or the macros of Wor

Learning to Code: Comments Count

I like comments in computer programming source code. I've never been the programmer to claim, "My code doesn't need comments." Maybe it is because I've always worked on so many projects that I need comments  to remind me what I was thinking when I entered the source code into the text editor. Most programmers end up in a similar situation. They look at a function and wonder, "Why did I do it this way?" Tangent : I also like comments in my "human" writing projects. One of the sad consequences of moving to digital media is that we might lose all the little marginalia authors and editors leave on manuscript drafts. That thought, the desire to preserve my notes, is worthy of its own blog post — so watch for a post on writing software and notes. Here are my rules for comments: Source code files should begin with identifying comments and an update log. Functions, subroutines, and blocks of code should have at least one descriptive comment.