All well managed product development projects are split into multiple phases, each distinct and each with it's own goals. Generally you begin with a proof of concept, request for proposal, short analysis or things like this. You follow this short cycle with a longer analysis, then a design specification, and finally you implement program. This consists of actual coding of programs and might include documentation as well.

Now you've got a finished project, and what you are supposed to do next is a quality assurance step. Generally, you want to test and test and test until program (or application system) exactly meets design specification (which should be treated as a sacred document) and associated standards manuals. It is critical to note that testing is done against specification and standards manual and nothing else at this phase of project.

When and only when you complete this testing and product 100% does what it was designed to do, then you create what is called an alpha test. This consists of sending code to a select group of users who will pound on product. Their job is to ensure that product works in field under conditions outside of your lab.

Once your product has been tested by some alpha testers, you may want to take some time to correct any issues, then perhaps send it out to alpha testers again. You might repeat this step one or two times until number of bugs found is significantly reduced.

HTML and website creation programs Graphics programs Perl CGI ASP Javascript Coldfusion

Those skills are great, but what many employers and clients REALLY WANT goes unsaid. What they do not tell you is this: They really want high-impact results. And you can get high-impact results by honing high-impact skills.

High-impact skills are: +designing to facilitate sales +search engine optimization, submittal and tracking +writing to sell +knowing how to increase traffic that results in sales +tracking success of ad campaigns