Woodie,

>>I am probably going to lose my job because of this thread.

That's pretty sad. Is there more to it than this?

Presuming you are young: if you feel you are in a rut, make sure you are not contemplating a jump to another rut. You seem to assume you want to stay a codehead; are you sure about that?

What about project management or design leadership? Do you enjoy figuring out solutions to problems and laying out plans to make it happen, or do you want to be in there coding to somebody else's design? Some here seem to be privileged to do all the planning, design and hands-on development in their projects; that was common for VFP work, but for larger corporate projects in dotNET that would be rare. And as automation increases, application design and management will move inexorably away from pure development. IMHO codeheads will become a commodity, competing with cheap foreign labor who can do an excellent job as long as a good scope is supplied. Just MHO.

Spend some time on visual interfaces as well- even take a class at your own cost. In 2004 the browser is prevalent and it needs developers who can create things that look good, or in a way that makes it easy for a web designer to make it look good. If you can do that, employers and other decisionmakers will remember you.

Overall: the market has changed and is changing at a huge pace. There are many more options than just what tool to become a codehead in next. Spare a thought for we old-timers who can cope with a new tool but not necessarily with the risk or upheaval of an entire career change!

Good luck,

j.R