Career change

[wxdqz]

I had a look at the other responses. In the main I have no qualms with them.For myself I have worked up through the ranks to where I am now settlinginto the role of Systems Architect. What this basically means is that Imust have the skills to work a project through from requirements gathering,analysis, design, implementation, testing and deployment. It doesn't meanI need to be an expert in all of these areas, just understand them well enoughto counsel in all of them, while mainly working on the first three areasmentioned.What is this leading to? Basically what I am saying is that before you becomea programmer, learn proper OO, component based methodologies. Too oftenthe emphasis is on the tools and technology without really understandingwhat system and applications are really all about. Engrave this on yourforehead: It is the business case that is important - everything is justa means to an end.Secondly, learn the language(s) you choose well. May sound like statingthe obvious, but I have come across programmers in many languages who reallydidn't know what they were doing. Sure, they could get a program to work,but never really mastered the tool. Trying to maintain their code was atrip into migraine land. Every language has its strengths and weaknesses,so learn them. Also, try not to get religious on it. It is the task thatis important - the tool is only useful if it is the best one to get the jobdone. There really is no one-size-fits-all tool.So far as languages go, I would say that VB, Java and C++ are the big three.You will probably find that a couple of scripting languages won't hurt either.Personally (and I can hear the snickers) I am also maintaining my skillsin C and COBOL. There are those who will understand so I don't need to explainit to them. To those who don't, trying to explain will be a waste of time.All the best. Hope this helps.