Path: utzoo!attcan!uunet!husc6!mailrus!ames!oliveb!intelca!mipos3!td2cad!brister
From: brister@td2cad.intel.com (James Brister)
Newsgroups: comp.misc
Subject: Basics of Program Design
Message-ID: <901@td2cad.intel.com>
Date: 20 Jun 88 04:13:35 GMT
Reply-To: brister@td3cad.UUCP (James Brister)
Distribution: na
Organization: Intel, Santa Clara CA
Lines: 24

This may be a stupid question, and I hope I'm in the right newsgroup.
Send any flames directly to me and I'll shut up.

For the past few years my professors have rambled on about data
structures, compiler design and more, ad nauseam. But none of them
have ever mentioned the best way, (or any way really) to go about
sitting down and actually writing a program.

What I mean is: do experienced programmers usually write flow charts,
or pseudo code. Do they write the whole program out by hand first or
build it up in their favorite editor?

What's a good way to organize the writing process? I have all these
great ideas running around in my head that I find difficult to get
out without making mistakes in the task itself.

If you want to reply to me personally, and if anyone else is 
interested, I will summarize any answers, and then post them.

+------------------------------------+----------------------------------------+
| Any opinions are my own and not    |   brister@td2cad.intel.com             |
| of my employer.                    |   USNAIL: 3065 Bowers Ave MS SC9-37    |
| (Corporations only have policys)   |           Santa Clara, CA 95051        |
+------------------------------------+----------------------------------------+