Re: How to apply (rather than understand) OO?
- From: "Alfredo Novoa" <alfredo_novoa@xxxxxxxxxxx>
- Date: 11 Feb 2006 11:56:41 -0800
Well, I suppose you and other OO users learnt OO somewhere but no with
books? Many OO books in the library are about OOAD and not exactly
about OOP. The second is usually about OOP in some language like C++ or
Pascal.
I learnt reading many books and articles, writing code and making
unnecessary and expensive mistakes due to the bad books, articles and
advices. I also learnt many things about OO reading non OO books. Many
OO concepts are simply renamed classic concepts, there are very few new
ideas in OO and even less new good ideas.
OOAD is not enough for database system programming and it has very
little substance covered with tons of obscure pompous verbosity.
Lahman's post are a very good example.
If you want to act like a DBA and an application programmer at the same
time you have to be good in both professions. You have to master OO,
relational and DBMS theory and to apply database science to implement
the business rules and the OO guidelines to the interfaces.
Many people try to do both things only knowing OO and the results are
always a disaster. Most comp.object participants fall into this group.
My problem is that I probably (or I think I do) need a way: "Silas, do
that and that and that".
You have to learn the theory and then to think by yourself ;-)
Otherwise you will be yet another monkey coder, and there are enough
here yet :)
Many languages allow mix procedural with OO methods, like Python, Ruby
and Tcl, but Java doesn't.
Java is a 100% procedural language.
See the definition of procedural language here:
http://foldoc.org/?procedural+language
You *need* to have at least one class to
start your project.
This is uninportant.
Am I wrong thinking in the "Java" way instead of
thinking that I can have a good program with OO in few places?
You might have a good application plenty of OO, but you also need to
use a DBMS applying database theory. The program is only a part of the
system and you have to design the system before the program. A good
design implies to separate the business rules and the presentation
rules. The business rules must be implemented in the DBMS and the
presentation rules in the program. To implement the business rules in
the program is a trogloditic approach and also what most OOAD books
teach.
About distinguish between application and system, I've probably already
done that. I'm a DB apps developer (still learning, but I try ;) ) so I
know it's rubbish using a loop to get the total amount instead of a
simple query.
Good for you!
And the same principle applies to any other business rule.
What's the next step?
To be sure that you are good in both database and OO theory and to put
your hands on the work. This is not so difficult.
Regards
Alfredo
.
- References:
- How to apply (rather than understand) OO?
- From: Silas Justiniano
- Re: How to apply (rather than understand) OO?
- From: muralikrishna151
- Re: How to apply (rather than understand) OO?
- From: Silas Justiniano
- Re: How to apply (rather than understand) OO?
- From: muralikrishna151
- Re: How to apply (rather than understand) OO?
- From: Silas Justiniano
- Re: How to apply (rather than understand) OO?
- From: Patrick May
- Re: How to apply (rather than understand) OO?
- From: Silas Justiniano
- Re: How to apply (rather than understand) OO?
- From: Patrick May
- Re: How to apply (rather than understand) OO?
- From: Alfredo Novoa
- Re: How to apply (rather than understand) OO?
- From: bruno at modulix
- Re: How to apply (rather than understand) OO?
- From: Alfredo Novoa
- Re: How to apply (rather than understand) OO?
- From: Silas Justiniano
- Re: How to apply (rather than understand) OO?
- From: Alfredo Novoa
- Re: How to apply (rather than understand) OO?
- From: Silas Justiniano
- How to apply (rather than understand) OO?
- Prev by Date: Re: How to apply (rather than understand) OO?
- Next by Date: Re: How to apply (rather than understand) OO?
- Previous by thread: Re: How to apply (rather than understand) OO?
- Next by thread: Re: How to apply (rather than understand) OO?
- Index(es):
Relevant Pages
|