Re: OO-Inquisition
- From: Alvin Ryder <alvin321@xxxxxxxxxxx>
- Date: 18 Apr 2007 20:14:24 -0700
On Apr 18, 1:17 am, coeval <hvfre...@xxxxxxxxx> wrote:
I am flaggerbasted how Topmind is treated in comp.object newsgroup.
Just for saying OO is not the dreamed "silver bullet" that would fix
all issues in software coding.
Many of posts are very blunt, people overacted, like Catholic Church
during The Inquisition.
People are scared of their IT carreer but less about the ease of
coding and maintaining an application. I work for 20 years of
programming, OO, SQL plus a lot database designs in Relationnal / OO
databases. As a pragmatic developer I made my own opinion about OO
paradigm. Basically Topmind is right, for "device code" OO is quite
useful but for large biz application coding by several teams and
numerous programers with different skills under budget/time
constraints, it has some pitfalls. It's not as good as it looks like
in in OO-books or in "OO-monks" preaches. begun my IT career as a C++
developer using Zortech and Glockenspiel C++ ersatz compilers coding a
middle size application (80 000 LOC) . All was done using all OO
features; inheritance, avoid if/then/else, switch/case... and so on.
After a couple of years of maintaining this application I noticed I
was improving/fixing more efficiently this application by
"refactoring" the database, I mean by changing the database and
migrating data rather than changing the OO code. That was a big shock,
what about is the OO "reuse" motto. In addition when my customer asked
to change some features in the application code, it was tedious to
pinpoint where/how to change the code, some part of the code was under
12 levels of inheritance, some functionnalities were spread in many
files, very hard to maintain and hard to read as well. Most of my IT
career I noticed programers writes code but they don't read it after a
while. Now, I push programmers to follow a strong coding guideline and
I review the final code every new build.
17 years later, I am still fighting with the "OO features" not in C++
but in Java. I am in charge to maintain, deploy, improve a large
application in Java (1.200.000 LOC) written by a 3rd company.
Formerly, connected to an OO-database and after 2 years re-designed to
use RBDMS database due to performance and database size issues. Same
as 17 years ago, I am still changing the database, as a workaround, to
fix and improve the application. For me and I am not the only person
to think that large, endless changing biz application is very
challenging to code using an OO techniques.
OO should be seen as a tool addressing specific issues in coding and
design, same as backtracking engine for gaming appz or expert system.
Coeval
My story is similar and I agree looking back C++, OOP and biz apps
weren't the best match in town. Of course they have their place with
operating systems, office apps, utilities, games, graphics, geography,
science, math, medicine, networking, searching ...
Thanks for presenting your real world experiences. I would rather read
that than (computer) science fantasies.
Cheers.
.
- Follow-Ups:
- Re: OO-Inquisition
- From: Phlip
- Re: OO-Inquisition
- References:
- OO-Inquisition
- From: coeval
- OO-Inquisition
- Prev by Date: Re: OO Principle - reference needed
- Next by Date: Re: OO-Inquisition
- Previous by thread: Re: OO-Inquisition
- Next by thread: Re: OO-Inquisition
- Index(es):
Relevant Pages
|
