There has been a great deal in the media about computer "hackers," those who tap into corporate and government systems as a lark. Theft is not the intention of the hacker, but the disruption to corporate record-keeping is immense. More important, the ease with which computer hackers have gained access to corporate computer systems has vividly demonstrated to everyone concerned the vulnerability of computer-based corporate and government activities. In that sense, the hackers have done the computer industry a service by creating this awareness.
Perhaps an even greater potential threat to computer confidentiality comes from dishonest and disloyal data processors within companies who use their knowledge and access for their own gain. How easy to add a couple of family names to a computer list of those to receive monthly dividend checks, or to sell vital corporate information to competitors. Blackmail is not unknown, either. There are a number of documented cases in which someone from a data processing department walked away with important records and offered to sell the information back to the company for a hefty fee.
As a result of all this, every business and government agency that depends upon computers not only must devote considerable attention to developing and running systems, but also must turn an increasing amount of attention and funds to securing those systems.
A business having between 150 and 250 DPers, if properly staffed, can spend $250 million a year or more for security professionals' salaries alone. Many companies, however, have not reached that point in staffing solely to secure systems, which opens up a whole new field for computer-security consultants. Those with intimate knowledge of computer systems are exactly the people to whom industry will turn for solutions to the computer-crime program.
In addition to devising security systems, there is also a need for procedures to be developed to screen out data processors whose ethical background is not what it should be, and to devise ways to supervise DP staffs to insure adherence to security procedures, also formulated by professionals.
As I've pointed out, successful entrepreneurs are the ones who see a need and fulfill it, and computer security represents one kind of opportunity.
Contract Programming
There is a trend in all industry to look increasingly to outside services to provide personnel to handle peak loads. The reason for this is obvious: maintaining a large permanent staff means higher overhead, even when the need for workers slacks off during quiet periods. Rather than over staffing, companies bring in specialists to augment the regular staff, which is cost-efficient. The cost to a company of providing benefits to permanent employees is high; more important, hiring and termination are very expensive and can cause a good company to earn a poor personnel reputation. This is why specialized temporary services and contract programmers flourish.
Because good programmers are in such demand, companies basically have three options when a rash of new programs are suddenly needed. One is to hire from the outside on a temporary, contract basis. The second is to over staff, bite the bullet when it comes to the overhead, and know that you have enough people on hand for the crunch. The third is to hire or train generalists who can shift from function to function, depending upon the needs of the moment.
What it all comes down to is that there is an excellent market for free-lance programmers to come in and reinforce permanent staff when needed. This can be a good opportunity for you, but there are problems to be considered.
First, the liability-insurance dilemma that is hitting many industries hard would have to be considered from your point of view as an independent programmer. Come in from the outside as an "expert," develop a program for a company that doesn't work and causes that firm to lose money, and you might be on the receiving end of a hefty lawsuit. The same holds true if you are functioning as an independent expert on computer crime and security and the files are stolen. In fact, for anyone starting a business, insurance must be one of the first things considered, and in many cases the cost proves prohibitive, and the insurance is hard to get at any price.
Another problem stems from how the government, particularly the IRS, defines a contract programmer. Currently, that definition is being pondered, questioned, and rewritten in Washington in an attempt to clarify when a person truly provides freelance services and when that person should be considered an employee of the company to which he or she provides the service. There is a long list of criteria that must be met for a company to avoid having to consider an outsider freelancer part of the permanent staff, and it's harder to justify where a programmer is involved. So much programming must take place on the company's premises, and programming projects put the freelancer on the job for protracted periods of time. Obviously, a company loses some of the benefit it is seeking if you, a contract programmer, must be considered permanent staff. If you decide to strike out on your own as a contract programmer, become familiar with the legalities. Check with a lawyer so that you can intelligently discuss the problems with a potential customer.
Despite these problems and others, we see more and more talented programmers going out on their own, and if you feel it's for you, there is plenty of opportunity for you to succeed.
