Hi ptum

I changed job 2 yrs ago from R&D "specialist" to a formal title of "business developer". I wanted more dirt (and occational tree splinters) under the fingernails, less analysis and reporting, more smell of program rubber hitting the road.

The team i joined wanted a "software architect" up front to structure and document their interim solunion (which of course had been put into production), so I did that, and followed up with architecture groupwork for the next generation of our product.

We then collectively decided on an iterative development practice, which meant that I and the lead developer did the overall tech. design of the application, including fitting it sensibly into an existing app. framework.

In parallel with that, i started some, partly "under the radar activities", including compiling statistics for our running solution (Perl including Win32::IE::Mechanize & GD::Graph) and setting up a project machine for automated documentation, build, test and deploy (CruiseControl, NAnt, NUnit, NDoc &c family of tools). That would be in a role as "tool smith" and "test coordidator/developer".

I sketch this story to underline, that in my current job i've worked maybe 10% in the role of my formal job title, and for the remaining 90% i've drifted into the niches needed by the project and seen by me as demanding and, - fun!
I leave the conclusion to you.

Best regards,
Allan

update... and hey! I managed to contribute mabe 25% solid C# programming too along the road, which actually was my original main motive to switch job, but as stated I found other goals along the road. "Navigare necesse est ..."