I work in a team of 7. We're a mixed bag of software, hardware, and systems engineering types, but we all have to do some programming as our primary function. When a team member leaves, the replacement gets all the lovely FNG assignments as their secondary role. That is, documentation, testing, and/or QA.
I got shoved into software QA when I arrived on the team. I joke about how I hate it and how my teammates hate me in that role, but I secretly relish it and my team mates know it has to be done.
Ask yourself these questions:
- Do you love processes?
- Do you find code reviews interesting?
- Do you like tearing into others' designs and implementation?
- Does it really jack your nads when the documentation doesn't jive with the implementation?
- Do you like audits?
- Do you like meetings?
- Do you like ISO 9001?
- Don't you just hate having to reverse-engineer a product because someone was lazy with the documentation?
- Do you like making/maintaining support tools?
Then Software QA is the move for you!
It is also a skill you can shop around regardless of the development environment (although some environments lend themselves to QA better than others).
...
And why is every word capitalised? Was this submitted by some spambot of sorts?
Because it's one of the generally accepted elements of style?
http://www.writersblock.ca/tips/monthtip/tipmar98.htm
Folks just don't understand proper writing anymore (my own posts notwithstanding)...
I might ask a cop for directions or report a traffic light being out, because that's something that is immediately useful.
An authority is a person who can tell you more about something than you really care to know.