Re: How to apply (rather than understand) OO?



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

.



Relevant Pages

  • Re: OOD/OOP and databases
    ... although I don't really see them as a design guide.... ... business rules is much more than validation. ... don't se much of this kind in the OO books. ... the Domain Model in two (on for validation like things, ...
    (microsoft.public.dotnet.general)
  • Re: OOD/OOP and databases
    ... I, too, have read many of the same books. ... You didn't mention the Design ... There are also a number of patterns books ... change the business rules, you need to encapsulate logic, not just ...
    (microsoft.public.dotnet.general)
  • Re: Complex Business Rules - Domain Model or Elsewhere?
    ... was wondering if there are patterns these days for holding complex ... I have found some books, ... The concepts in the book and website are about how to specify complex business rules as automated test suites written in a form that is easy for the business analysts to understand, author, and manipulate. ...
    (comp.object)
  • Re: Translations from UK to US
    ... : No - I have no gone to the extent of saying directly what the British: idiotshave regularly: posted as insults to the intelligence of the American children reading: the books. ... I have made it clear that there was NO effort by the editors: and author to simplify the books. ... Titles have been changed regularly -: the first books in France uses the title Levine suggested for the: American Version - and I have not heard your outrage about that. ... So it does not reflect on the language itself. ...
    (alt.fan.harry-potter)
  • Re: In the Matter of Herb Schildt: a Detailed Analysis of "C: The Complete Nonsense"
    ... know, as Seebach seems not to, that all ints are floats and all floats ... independent of a set of facts about a specific programming language. ... If you like to learn from books, ...
    (comp.lang.c)