OO is a conceptual tool, and therefore it falls under the rule: "Use the right tool for the problem at hand." Same goes for DO. The problem are guys (and gals)

OO is a conceptual tool, and therefore it falls under the rule: "Use the right tool for the problem at hand." Same goes for DO. The problem are guys (and gals) who have learned how to hold a hammer (but little else), and therefore treat everything as a nail. OO has undoubtedly been extremely overhyped. Unfortunately the backlash is not as hard as it should be, because by now OO is so firmly entrenched in the corporate sector that it will take (at least) one generation to merely flush it out of the fields where it doesn't belong at all. That said, sometimes OO might be just what you want to finish the job cleanly and on time. [Edit: typos]