CG> Flow charting is also very important.  If you can't organize and
CG> diagram  chunks of a program on paper, you are going to have
CG> problems trying to organize the source code.  Those nice
CG> little plastic templates with diamonds and squares should
CG> be one of the first tools purchased towards a programming
CG> career.
     Unfortunately, when I was a teen I bought a
well-used typewriter and started typing on my own, no
lessons, no touch type.  55+ years later I'm still
typing that way.  I can do pretty good, but I wish I'd
learned to type properly.
     A similar situation pertains to my programming.
My roommate was assigned to the maintenance crew of a
main frame.  I was very interested in it and he gave me
a list of the machine language commands.  I was writing
minor programs for it before I ever saw it - and never
heard of flowcharts.  Eventually, he sneaked me into
the building on a Saturday and I got to play with it -
and run my programs.
     I was so taken with the machine I applied for
membership in that group.  I had to agree to remain
with the "firm" an extra year.  These were delicate
negotiations since I wasn't supposed to know the thing
existed.  When I was properly introduced to the
machine, I had to Oh and Ah at the proper places like
I'd never seen it before.  As you've probably noted,
even after almost 50 years, I'm still circumspect when
I talk about it.
     I really don't know if the proper training would
have helped: I am the type who forges ahead and only
reads the directions when all else fails!  But yes, I
would recommend learning flowcharting (and touch typing).
I only do it when I can't find the end of this piece of
spaghetti!
  FIDO: Bill White @ 1:135/110 (Miami)
 InterNet: bill.white@110.sunshine.com
 * SLMR 2.1a * If you cannot measure output, then you measure input!
--- Maximus 2.01wb
---------------