Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-pcd!hplsla!jima
From: jima@hplsla.HP.COM (Jim Adcock)
Newsgroups: comp.object
Subject: Re: What is OOP / OOD
Message-ID: <9450015@hplsla.HP.COM>
Date: 11 Oct 89 21:50:03 GMT
References: <1989Oct2.161552.14306@polyslo.CalPoly.EDU>
Organization: HP Lake Stevens, WA
Lines: 26

> yost@esquire.UUCP (David A. Yost) /  7:23 am  Oct 10, 1989 /
>In article <9450002@hplsla.HP.COM> jima@hplsla.HP.COM (Jim Adcock) writes:
>>At least read several different books, ... so that all the dogma you
>>get exposed to from various sources will start to cancel out.  Finally,
>>spend more than a superficially amount of time programming in the different
>>languages ...
>
>It's too bad that 99% of us will never have time to do these things
>nor have the authority to pick the language we prefer to use, and
>so what we end up using will be whatever language musters the most
>PR/buzzword/advertising/backward-compatibility/hearsay/availability
>momentum.

Well, one technique to learn a bunch of Object Oriented Programming Languages
is to choose one--as you suggest based on PR/buzzword/management-dictate etc,
and then when your programming project fails based on that choice, you then get
to go back and learn another OOPL.  I think for most people, making the 
wrong choice once will either smarten them up enough to make a good choice
the next time, or to drive them out of Object Oriented Programming 
altogether.  Ideally, one would work for a company that knows "on-the-job"
training is the most expensive.  But on-the-job training can be effective too--
just not as cost/time effective.

I would encourage people who make/are-given a bad first choice of OOPLs not
to give up on the field, but rather to go back, study the other languages, and
go for a more reasoned choice the second time.