Reuse is on people and education, not Just Architecture

?

Reuse is on people and education, not Just Architecture

Jeremy Meyer

You might adopt the approach. A framework that's well designed, or an architecture so is carefully considered and C Leverly implemented, would lend itself to reuse within your organization. The truth is this even the most beautiful, elegant, and reusable architecture, the framework, or system would only being reused by People who:
Know it ' s there
Within your organization, developers or designers need to know that a design, framework, library, or fragment of code Exis TS, and where they can find all the critical information about these elements (e.g., documentation, versions, and Compatib Ility) in order to reuse them. It's a simple, logical truth this people won ' t look for things that they don ' t believe exist. Likely to suc-ceed with reusable elements if the information about them is "pushed."
There is any number of methods for pushing information on reusable elements in an organization. These range from wiki pages with a RSS feed providing update information, useful in very large teams, to email announcing Version updates in the source repository. In a tiny team, the designer or lead developer can inform he colleagues in personal conversations or by shouting it Acros s the office. Ultimately, whatever your process for communicating on reusable elements, make sure it's One-don ' t leave it up to C Hance.
Know How to use it
Understanding how to reuse a element depends on skills and training. Of course there is those people who (to use Donald Knuth's terminology) "reso-nate" with coding and design. We have all worked with them, the gifted devel-opers and architects whose speed and depth of understanding are impressive,
??? Things every software Architect should Know
?
?? Even scary. But these people is rare. The rest of your team might is made up of good, solid, intelligent developers and designers. They need to be taught.
Developers and designers might not know of the particular design pattern used in a design, or fully understand the inherit Ance model, the Frame-work designer intended them to use. They need to being given easy access to that information in the form of up-to-date documentation, or even better, training. A little training goes a long-toward ensuring that everyone was on the same page then it comes to reuse.
is convinced that it ' s Better Than doing it themselves
People, and particularly developers, tend to prefer to solve problems themselves rather than the ask for help. Asking how something works are a sign of the weakness, or even an indication of ignorance. This have a lot to does with the maturity and personality type of your individual team members; "Better than doing it them-selves" means different things to different people. The ' Young Guns ' on your team would always want to write things themselves because it appeases their egos, whereas your MOR E experienced people is more likely to accept that someone else have given thought to the problem domain and have something To offer in terms of a solution.
If your team doesn ' t know where to find reusable artifacts or what to reuse them, they would default to the natural, human P Osition:they would build it them-selves. And you'll pay for it.
Jeremy Meyer have been designing and developing software for nearly years, as well as teaching its mastery. He is currently a principal consultant for Borland Software in its modeling and design space.

Reuse is on people and education, not Just Architecture