Re: Retrieving unnecessary data

ShaneLM <shane.niebergall@xxxxxxxx> writes:
Wow...thank you so much to everyone who responded. You've cleared up
some of my misunderstandings with OO, and I now feel like I've got a
much better grasp on the problem at hand.

It is still possible to find signal in the noise of Usenet.

One last comment - Topmind mentioned that OO is a fad and should not
be used in the context of business applications. Do others agree?

No. Over the past few years I've been spending a lot of time
developing systems for both the financial services industry and the
telecommunications industry (a combination that flows naturally from
my misspent youth in CASE tools and broadcast video). I can assure
you that OO techniques are used extensively to develop a wide variety
of applications in those domains.

Then do you suggest procedural programming instead? I find it so
hard to believe that many colleges, books, etc are mislead,
especially when some of the design patterns seem so elegant.

They're not misled.

I can understand how OO is not best for all projects, but to say
it's a fad is shocking to me

Recognizing that no one tool is appropriate for all jobs and, by
extension, that different tools have different costs and benefits in
particular domains, is essential to being able to produce quality
software. You've passed the first bar I set when interviewing
developers. ;-)

BTW - i know I risk opening a can of worms with that question, so
let's not. I'd just like to hear a few opinions.

Yes, you probably have opened a can of worms. When reading the
responses, you should pay attention to who is writing from experience
and who is simply ranting. I found that comp.object improved
dramatically when I made two additions to my killfile. Your milage
may vary.

Regards,

Patrick

------------------------------------------------------------------------
S P Engineering, Inc. | Large scale, mission-critical, distributed OO
| systems design and implementation.
pjm@xxxxxxx | (C++, Java, Common Lisp, Jini, middleware, SOA)
.