| || |
To go Technical from Analytical
Need suggestions for career growth? Have 5+ years of QA analyst experience. Certified with CSQA and CSTE. Would like to pursue QA + technical. Have basic programming exposure.
How to switch to analyst cum technical person? All ideas will be welcomed.
Re: To go Technical from Analytical
What sort of technical expertise do you want?
I've somehow become the "techie" of my department - despite having come from somewhere where I wasn't considered very technical at all.
Here's my story - I took a short (3 month) certificate course in "IT" - learned basics of networking, OS installation, hardware setup and Access. It was sort of an umbrella course designed to get your foot in the door. It got my foot in the door (as a tester [img]images/icons/blush.gif[/img] ) and since then, my learning has been online and user experience. Everytime I come across a technical problem, I try to figure it out myself first before going to anyone for help. Nine times out of ten, I figure it out. The internet's a great resource once you learn to navigate it. I've been learning everything on a need-to-know basis also. I find it sticks better if I'm actually going to be using it then if I'm just learning to know it (that's just me, however).
So, my suggestion is take some courses for foundation and then tackle tech problems as they come your way.
Re: To go Technical from Analytical
<font size="2" face="Verdana, Arial, Helvetica">If you want to learn technical things, it depends, as Plummi stated, on what you mean. Some people consider certain "test techniques" to be more "technical" than others and, as such, that might be a way to broaden out more of your experience. Some aspects of performance modeling and capacity planning are considered more technical aspects to the general concept of testing as well.
Originally posted by Michael Beven: How to switch to analyst cum technical person? All ideas will be welcomed.
My advice here is to have some idea in mind for a program that you want to write and then learn the language in the context of writing that program. That tends to be a helpful impetus for many people. All of this translates into being able to come up to speed quickly on automated test tool languages as well, such as the Visual Basic-like language behind Rational's Visual Test and Robot to the more C/C++ facsimile behind 4Test (in Segue's SilkTest) or even in Mercury's WinRunner TSL. I was also able to translate this into game writing, such as by learning how to program in the SCI language (based on LISP and Smalltalk) or in languages like Inform, TADS, and Hugo (all based on C and C++, for the most part).
You can also learn the basics of other forms of testing that lead into more technical areas such as networking. For example, you can learn about security and vulnerability testing and this will often teach you things about encryption as well as general networking technology protocols and various other elements related to that. That, in turn, can lead into considerations of how networks are constructed. (You can read books like Hacking Exposed or High-Performance Networking Unleashed. Another thing I did was buy the book Developing Your Own 32-Bit Operating System and wrote my own operating system based on the examples in the book. I also learned how to write my own compilers from various freeware sites on the Web.
There is not set formula on how to "become" a technical person so what you have to do is find out what will work for you given how you best learn things and, right now, only you know that. But I recommend defining what you mean by "technical" and then forming goals based on that definition and then finding solutions that can help you satisfy those goals. If your goal is to learn as many scripting languages as possible, you can take the list I gave above as a good starting point. If your goal is just to get generally familiar with any scripting language, you could choose just one and concentrate on that. You also have to determine how you best learn: is it via self-directed learning or are you better in classroom settings? That can be an important determinant in how you should go about gaining technical knowledge in a given subject.