New Skills for Software Testers and Software QA Engineers: 2013 … and Beyond!

[article]
Summary:

Let's take a look into the future—all the way to the year 2013! As a software tester or software quality engineer, are you planning to learn a new skill in the new year. If you are, make sure you approach it in a way that will make that skill stick.

A title like “New Skills for 2013” creates some expectations in my mind, and I am sad to say that they are not particularly good. In a publication like this one, one might expect a statement like “technical skills are increasingly important for software quality and software testing professionals,” followed by a list of buzzwords and, just maybe, some comment about soft skills at the end.

Given how many books I have in my office about "learning the technology of the day in twenty-four hours" and the amount of dust accumulating on those books, I am reluctant to write yet another article like that. Instead, I'd like to talk about the three things it takes to make a skill stick and to improve your chances of moving from "bought the book" to "actually competent" in a new skill, whether it is a technical or soft skill.

When I think of my ideal learning project, I look for the intersection of three things. First, my skill set should be near the problem, but not an exact fit. Second, I want meaningful work to do. And, third, I need someone to call for help when I get stuck.

A Skill Set Near The Problem
Over a decade ago, I was working on a large program written in C, mostly expressed in one file. We make jokes about bad code (and it was), but the program ran every month and created real revenue for our company.

One of my colleagues, Jeff Klein, was a wizard with the code. He could quickly find things that no one else could. Jeff didn’t have the program memorized. He had a power-editing tool. It made the screen fly by. One day, I asked Jeff what he was using and he said Vim, which comes standard on most versions of UNIX.

In college, I had to use Vim’s earlier incarnation, vi, on some systems. It was more than a little intimidating, but other programmers had learned it, so I sat down with the Vim Book for a few hours. After that, I used Vim over and over again for a few months. It took time, but I eventually became a Vim wizard, too.

About the author

Matt heusserm's picture Matt heusserm

The Managing Consultant at Excelon Development, Matt Heusser is probably best known for his writing. In addition to currently serving as managing editor of Stickyminds.com, Matt was the lead editor for "How To Reduce The Cost Of Software Testing" (Taylor and Francis, 2011). He has served both as a board member for the Association for Software Testing and as a part-time instructor in Information Systems for Calvin College.

StickyMinds is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!

Upcoming Events

Oct 12
Oct 15
Nov 09
Nov 09