B. How to Become a Computer Consultant

The first key point to realise is that you can't know everything. However you mustn't become an expert in too narrow a field. The second key point is that you must be interested in your subject. The third key point is to differentiate between contract work and consultancy. Good contractors move from job to job every few months. A consultant is different. A consultant often works on very small timescales – a few days here, a week there, but often for a core collection of companies that keep coming back again and again.

There's a lot of work out there for people who know Visual Basic, С++, and so on. And there are lots of people who know it too, so you have to be better than them. Qualifications are important. Microsoft has a raft of exams you can take, as does Novell, and in my experience these are very useful pieces of paper. University degrees are useless. They merely prove you can think, and will hopefully get you into a job where you can learn something useful. Exams like Microsoft Certified Systems Engineer are well worth doing. The same goes for NetWare Certification. However, this won't guarantee an understanding of the product, its positioning in the market, how it relates to other products and so on. That's where the all-important experience comes in.

Here's the road map. After leaving university you get a technical role in a company and spend your evenings and weekends learning the tools of your trade - and getting your current employer to pay for your exams. You don't stay in one company for more than two years. After a couple of hops like that, you may be in a good position to move into a junior consultancy position in one of the larger consultancy companies. By the age of 30, you've run big projects, rolled out major solutions and are well known. Maybe then it's time to make the leap and run your own life.