An anonymous reader writes ""As developers, once we start separating our code into abstract ontological typologies, we make use of the human mind's phenomenal ability to work with types. Our code becomes less about jump tables and registers and more about users, email messages and images. What once was a problem of allocating resources and operations within the computer becomes an abstract, logical problem within a collection of objects. Like children awe-struck by stories of magicians of old, speaking incantations and pressing their wishes into reality by the power of their mind alone, we become drunk with the sense of awe and possibility." HTMList.com contributor Edgar Hassler dives into the pitfalls and payoffs of code reuse and how best to approach it in web-based applications." Link to Original Source
This discussion was created for logged-in users only, but now has been archived.
No new comments can be posted.
Reduce, reuse, recycle: Writing code for reuse 0 Comments More Login /
Get More Comments