comment on

This strikes me as unusual, usually the support and testing guys want to get into development not the other way around.

Quite. I'm thinking my path would be more in terms of operations (speccing new equipment reqirements, network design, bandwidth needed, monitoring, maintenance) and in terms of QA and release control (automated testing, random testing, continuity, focus groups).

For example, when Scott Cook of Intuit was building Quicken, he (or one of his guys) would plonk themselves down beside amateur testers and watch how they used the software. Every time the tester ran into a problem, the programmers would be told where the problem was, and to simplify or clarify the interface.

I guess I'm getting to the point where I can say, "Development? Yeah, done that.", and be able to move on to the next thing. The most obvious step to me right now is Operations and Support.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

In reply to Re^2: OT: Testing, operations and support resources by talexb
in thread OT: Testing, operations and support resources by talexb

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks