Monday, May 08, 2006
This Object oriented design (and implementation)
I think OO methods are not the best thing for software design!
Listen! Listen!!
You have a problem. You designed it OO way perfectly. Implemented. Fine.
Now when it comes to change, there's hell lot of changes to be made. If you have to stick to the original philosophy of the design. It will take unacceptable long time, and you tend to compromise!
Why was this happening? Because the analogy of the design with real life (everything is an object and each has its characteristics) is NOT profitable for us.
The real life has evolved for millions of years, the species, the sub-species ...
Our objects are not evolved like that, and we want them to change/evolve faster :D
getting me?
:)
I think OO methods are not the best thing for software design!
Listen! Listen!!
You have a problem. You designed it OO way perfectly. Implemented. Fine.
Now when it comes to change, there's hell lot of changes to be made. If you have to stick to the original philosophy of the design. It will take unacceptable long time, and you tend to compromise!
Why was this happening? Because the analogy of the design with real life (everything is an object and each has its characteristics) is NOT profitable for us.
The real life has evolved for millions of years, the species, the sub-species ...
Our objects are not evolved like that, and we want them to change/evolve faster :D
getting me?
:)
Comments:
hmm, but we gotta get that software out in months and cannot wait for a loong time for it to evolve like humans
Post a Comment
# posted by 
: 3:51 PM
: 3:51 PM