Riuso e OOP today are in the mood to repeat the obvious.
course you happened (or will happen) to live the following experience:
your boss / manager tells you that you have to perform a given task, to complete a project, etc.. and it would be better to use
reuse of parts of this or that existing project.
Eye, now comes the obvious:
the operation is convenient if and only if the planned departure was conceived, designed and written strictly OO , otherwise this is what happens:
- you find yourself copying / pasting procedures or parts of procedures
- soiled with your application code out of context
- build your code on the ruins of another project, resulting in a botched design, precluding the possibility of finding a better solution.
This kind of reuse Italian is part of the sad legacy, also known as "the art of getting by," as applied to the process of software development:
- STEP ONE: Write a small program in a hurry, not document, do not even think about a design. Oh, one more thing: whatever the language of choice if you must use them, use only the objects pro-forma, tries to do everything in a procedural way (I know you can not be modest). - STEP TWO: When will an application to solve a similar problem in some way, your successor (Because in the meantime you'll be gone for the technical manager from the competition) will take the old sources, and in an attempt to bring up something decent in the time required to make a soup:
- reverse engineering your code
- bug fixing of your code
- cross-design between the old application and what you would like
- changing the coding procedures (ie core of your program)
this course without realizing it without a schedule that gives a name to the various stages of development, and finally calling the above soup programming .
This is why it is a good idea to use class libraries ready (and there are companies whose business is to sell its components), while generally a bad idea to try to reuse code written in a hurry to solve a problem.
0 comments:
Post a Comment