Mon premier blog

Object-Oriented Design Heuristics Arthur J. Riel
Publisher: Addison-Wesley Professional

Mar 6, 2014 - When designing tabbed objects, such as properties and preference windows, ensure that the visual design makes the scope of a restoration button clear. Individual tabbed “cards” should be visually separated from the surrounding window so that .. In fact, many early GUI's were built entirely in non-object-oriented environments. As Steve Freeman and Nat Pryce wrote: “What matters most is the context in which the collaborating objects are used. Don't hold too rigidly to these classifications; they're more like heuristics. In Arthur J Riel's Object-Oriented Design Heuristics, a book of metrics for good object-oriented design, he states: I refer to these 60 guidelines as “heuristics,” or rules of thumb. Riel has captured this elusive, subconscious list, and in doing so, has provided a set of metrics that help determine the quality of object-oriented models. In Refactoring by Martin Fowler. They appear within the user's environment and may or may not map directly to an object-oriented program's object. May 12, 2011 - Encourage that type of autonomous thought. The Fortress blog has a recent post, Why Object-Oriented Languages Need Tail Calls, where Guy Steele argues for the necessity of proper tail call implementations without rehashing two of the classic arguments: state machines and the continuation passing style. Closely related, see Replace Conditional With Polymorphism in the same volume; Bob Martin also has quite a bit to say on the disadvantages of switch statements in Clean Code (for example, heuristic G23 Prefer Polymorphism to If/Else or Switch/Case). Sep 25, 2011 - Experienced developer Arthur J. The authors divide an object's peers into three categories: Dependencies, Notifications, and Adjustments (DNA). However, since object-orientation, like any other good paradigm, can be a powerful tool but is not a silver bullet, are there times when using an enumeration is a good decision? Nov 1, 2012 - The book has a chapter on object-oriented design styles, and includes a description of “Object Peer Stereotypes” that addressed my conundrum perfectly. It starts by From the generic no-stack design, one might express a 'generic TCO' which simply reuses the same activation-record - no matter where it is allocated (i.e. Sep 12, 2005 - 我是从csdn的一个Blog里知道这本书的，下来一看，很奇怪的书名，很通俗的文风。今天读了Chapter1-2，觉得Arthur J. Sep 15, 2010 - Software design fundamentals, The design process, design fundamentals, effective modular, design dataflow oriented design, transform analysis, transaction analysis, design heuristics, object oriented design.