Re: Classic Traps -- I need your input!

I don't know if it's considered a Trap or not, but the lionshare of my time,
when correcting/enhancing old code is spent pgup and pgdn'ing because it
doesn't embrace object oriented technique enough.

In other words, say you have a program that does a letter extract. It
prompts the user for three-level selection criteria, each dependent on the
previous, and then prints the letters. And it's one, 20 page program, with
only the last 2 pages containing subroutines.

I don't suggest that people try follow the strict code of some manifesto of
OO, but just think in peices. Smaller peices. When your brain is deciding
how to lay out a solution, know how to compartmentalize your processes into
neat packages. Thinking this way, most people will find that things like
using subprocedures, and local variables, and modules, and even service
programs come naturally. Documentation is still a key to understanding
code, but how well can you document a 20 page or longer PROGRAM, unless of
course, you know in advance all the changes that will be made to it, ever.

I could write for hours on this topic, as you probably could also, and I
would be willing to elaborate, if this is the type of topic that fits.