Skip to main content

Know the Job Market

I tend to answer questions when asked, often without pausing long enough to consider the best wording — or even if I should answer.

This semester, I'm teaching a course that uses Wikis to explore collaboration. The students are struggling with the Wiki format and some of the concepts. You'd be wrong if you thought users of Wikipedia understood how the system functions. I mentioned that installing and maintaining any content management system (CMS) was a good skill to have.

A student then asked about job skills currently in demand. He was told by someone that some specific tools were in demand, while others were not. The tools and skills he was told are valuable are absolutely, positively not highly-valued based on a simple search of tech-focused job sites. And, of course, I said so.

Sorry, but Visual Basic isn't going to land you at the top of the field. (There are still companies using VB for database applications, but C# is a better choice in my view.) And while COBOL is interesting (yes, we teach COBOL and MUMPS) it isn't going to expose you to modern OOP coding techniques. COBOL is still in use but it is not going to be hot career path for most IS graduates.

My blunt assessment of demand: it helps to know C-based languages, basic SQL (there are minor variations), Windows administration, and Unix networking tools. If you want to program, focus on the tools of portable computing: Objective-C (Apple), C# (Microsoft), and C++ (Android). My view, and some disagree, Web skills aren't the "sweet spot" of the job market anymore. Apps rule. If you want a good source for demand in tech, visit Dice and read their talent surveys, which are updated annually in the spring. The link is: http://marketing.dice.com/techtalentdemand/

I should have said that what the university teaches doesn't matter: programming skills transfer. I should have said that the theories are transferable. I should have said many things — but the reality is that employers want to hire people with specific skills. In this economy, if an employer can hire a C# programmer, they will do that instead of hiring someone in need of additional training.

Students deserve the truth. We are not preparing them for the job market as it is or as it will be. We are preparing them for the job market of five or even ten years ago.

We'd like to imagine that employers value the skill of learning — but the reality is that human resource departments will have checklists of keywords. Do you know Ruby on Rails? Are you familiar with HTML5/CSS3 fluid layouts and/or responsive grids? Do you know Objective-C and Cocoa Touch for iOS development? It's all about having the right keywords for a specific job.

And I said so tonight.

Get certifications. Complete free online courses. Do whatever it takes to have the skills companies want. It's not enough for your résumé to state "Familiar with Object Oriented Programming concepts." Which languages? Which tools? Read the local job openings on Dice, Indeed, Monster, and other websites. What do companies and organizations want? Be the employee they will want.

The market moves quickly. Schools need to adapt quickly, too. The tools do matter, even if we wish the focus could be on theory.

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.