Not good enough just to be a C#/SQLserver expert?

[HairyArsedBloke]

"solutions architect" - in that case fowler et al should do you well as a starting point.

but you'll sometimes find that people want a "highly skilled specialist who can craft robust, elegant, maintainable and re-usable code" as well as have a look at some legacy stuff hanging around on the server (like a bad smell) and also deal with some broken integration stuff which handles xml batch feeds and also perhaps sit on a db for a day or two while the dba gets back from hols. iow it often depends on why you're being called in...to architect & develop a greenfield app (nice) or to babysit some malfunctioning horrorware that noone else will touch. but ime & aoan a combo of both.

You are describing HAB Inc. on a good day

[scotspine]

"solutions architect" - in that case fowler et al should do you well as a starting point.

but you'll sometimes find that people want a "highly skilled specialist who can craft robust, elegant, maintainable and re-usable code" as well as have a look at some legacy stuff hanging around on the server (like a bad smell) and also deal with some broken integration stuff which handles xml batch feeds and also perhaps sit on a db for a day or two while the dba gets back from hols. iow it often depends on why you're being called in...to architect & develop a greenfield app (nice) or to babysit some malfunctioning horrorware that noone else will touch. but ime & aoan a combo of both.

[HairyArsedBloke]

You've just reminded me - I upset the C# guru at one of my clients last week by using something that he didn't know about: the continue statement. He said he'd never seen it before.

Mind you, he was right that using it is a sign of a rubbish design.

[xux42]

Ever thought of leaving all that behind and moving up the ladder to tech arch, TDA, tech PM, migration projects etc??

This kind of role often requires a good all round background, though not necessarily all hands on.

PZZ

Thanks for the quick responses.

Yes indeed I am quite happy to become a solutions architect. I think its vital to demonstrate sound knowledge of concepts, and the capabilities and pitfalls of the technology the developers are using though.
I know as a developer how important it is for architects, managers and analysts to maintain credibility in the eyes of the guys actually building the apps.
This is why I'm doing some hands on C++ & true OOP as well as immersing myself in C#3.0/SQLServer.

PS what does 'TDA' stand for?

[Zippy]

I'd go straight for c# myself.
They want experience in ASP.NET as you can do a lot of simple stuff with the IDE without writing any code.
Amongst other things, you'll need to know how to handle XML if you are dealing with webservices.
You'll need some basic web server admin skills to build and maintain your own (desktop) dev environment.
You'll still be required to write elegant, re-useable code.
My last contract involved all of the above and the reason it was required was because they could only afford one techie. Oh what fun

[pzz76077]

Ever thought of leaving all that behind and moving up the ladder to tech arch, TDA, tech PM, migration projects etc??

This kind of role often requires a good all round background, though not necessarily all hands on.

PZZ

[xux42]

My experience is in corporate Financial Services Mainframe/C/VB Procedural design/programming and a smattering of analysis. That has served me well, but the bottom seems to have finally fallen out of the market.
So I'm building on my rudimentary C/VB Object Based knowledge by working through the Deitel C++/OOP book as a stepping stone to VS2008/C#/SQLServer2008.
I plan to use the .NET Express/Framework/SDK downloads with Troelsen's Pro C# & MS Programming SQL Server books to complete the job.

So, finally getting to the point
- any views on the path I'm following?
- any views on why C# / SQLServer Job adverts also frequently cite ASP, XML, a list of obscure software products and look for server/webserver admin skills as well?
Why would an employer want a jack of all trades rather than a highly skilled specialist who can craft robust, elegant, maintainable and re-usable code as part of a team?