|
Category: Computers & Technology : Programming
I've been programming for over 20 years, and have taught programming at a local college. What I write represents my opinions and my experience.
First, some terminology:
A successful program is something users "run" to produce desired results. To produce this program, good programmers write specifications, write code, "compile" the code, then thoroughly test it.
If it doesn't work, they then find and correct the errors. They may, in the process, revise the specifications and rewrite much of the code.
(A good program will also be tested on new users. Their opinions and feedback are most helpful in revising the program to make it more useful and easier to use.)
Programs take a long time to develop, even simple ones, and they must be almost totally correct to work well.
The most important thing for an aspiring new programmer (you) is to have enough excitement and perserverence to fight or overcome the inevitable irritation, frustration and discouragement, because everything takes much longer than you ever suspected, and work in ways you never thought of.
With that in mind, what you need is much like what you need to build anything: you need a good idea of the finished product, and skill to transform the start materials to the finished product.
Specifications
You need a good idea of what you want the program to do.
This will be fleshed out again and again until it becomes quite exact. Generally speaking, the more time you spend writing out descriptive material -- what the program will do and how the program will do it -- the more time you'll save later on.
For every hour you spend writing these specifications, you'll save two or three hours later. (In fact, saving five hours for every hour of writing specifications is not uncommon). You'll have less errors and less re-writing of code.
Programming
You need to know how to program, which may involve taking a course or reading a book. Of course, you need a computer (you buy this), and a compiler or interpreter (you buy these too), and perhaps a word-processor type thing. The word-processor type thing is the tool you'll use to write the specifications and code for your program.
The compiler will change the code in form into a program the computer can run.
Frequently, programs require libraries of routines
(pre-written code). For efficiency reasons, it often pays to buy these rather than write these
yourself.
The best thing to have is a class, not because you get free use of hardware and software, but because you often get free consulting on your own projects.
Someone who is willing and able to answer your
programming-related questions is invaluable.
For example, Windows-compilers provide hundreds of library routines. Some require intricate set-up.
If you're writing a Windows program, it pays to ask the advice of someone experienced in it.
Debugging
Beginners make one or more errors for every five statements of code that they write.
Finding these errors ("bugs") is not simple. Compilers will find some of these errors; but complete "debugging" requires someone with an understanding of the program and what it is supposed to do, who is willing to learn and apply debugging techniques -- in short - YOU. It takes time to debug.
In my experience, experts spend 20% of the time writing code, and 80% of the time testing and debugging it. (and 0% of the time documenting it)
(that was a joke).
For beginners, it might be 5%, 95%; even 2%, 98%.
Frequently the software tools themselves have errors or "subtleties" (errors) that are not easy to fathom in advance. Give yourself time and patience.
|
Submitted By
|
Asha Goldberg |
|
Description
|
business consultant |
|
Web Page
|
not
available |
Other Articles in this Category
 What is Visual C++?
by David Goldbrenner
How to Learn Database/SQL Technology
by Ravi Iyer
Other Sites
Storkin.com - Baby and
Pregnancy Tips and Discussion
Health Articles
Menopause
Symptoms
HIV/AIDS
Symptoms
West Nile
Symptoms
Diabetes
Symptoms
Pregnancy
Symptoms
Tech Sites
Dell DJ Hacks
Read other Articles -
click here.
|
