Wanted pages
From CSSEMediaWiki
Showing below up to 100 results starting with #101.
View (previous 100 | next 100) (20 | 50 | 100 | 250 | 500)
- Piecemeal growth pattern (1 link)
- Word Association Football (1 link)
- Gateway pattern (1 link)
- Move field (1 link)
- Portland patterns repository (1 link)
- With apologies to the late great Douglas Adams. (1 link)
- You aint gonna need it (1 link)
- Query object pattern (1 link)
- Gang of four 1995 (1 link)
- PS Library (1 link)
- Naked objects (1 link)
- Eclipse (1 link)
- Application controller pattern (1 link)
- Two step view pattern (1 link)
- Whole part pattern (1 link)
- Xerox PARC (1 link)
- Class names should be nouns (1 link)
- Reconstruction pattern (1 link)
- Presentation abstraction control (1 link)
- Identity field pattern (1 link)
- Adele Goldberg (1 link)
- Anaemic domain model (1 link)
- Brother, nephew and me (1 link)
- Record set pattern (1 link)
- Layers pattern (1 link)
- Party Of Five 1996 (1 link)
- Operational Data Store (ODS) (1 link)
- Replace Type Code with Subclasses (1 link)
- Association table mapping pattern (1 link)
- Value object pattern (1 link)
- Unit testing (1 link)
- CppUnit (1 link)
- Shearing layers pattern (1 link)
- Implicit lock pattern (1 link)
- Peter Coad (1 link)
- PLOP One 1995 (1 link)
- Open-close principle (1 link)
- Template:Ffd (1 link)
- Registry pattern (1 link)
- Master slave pattern (1 link)
- Eliminate unnecessary classes (1 link)
- Pipe and filter architecture (1 link)
- Waterfall process (1 link)
- Class table inheritance pattern (1 link)
- Seperation of concerns (1 link)
- Alistair Cockburn (1 link)
- PyUnit (1 link)
- Inheritance mappers pattern (1 link)
- Martin Fowler 2003b (1 link)
- Party Of Five1996 (1 link)
- Open/close principle (1 link)
- Managing IT resources (1 link)
- Principal of Least Knowledge (1 link)
- Remote facade pattern (1 link)
- Microkernel pattern (1 link)
- Generalize object into a class (1 link)
- Service Oriented Architecture (1 link)
- Client session state pattern (1 link)
- Chrysler comprehensive compensation (1 link)
- Avoid redundant data (1 link)
- Throwaway code pattern (1 link)
- Keep behaviour and data together (1 link)
- Layer supertype pattern (1 link)
- Extreme Programming (1 link)
- Single Responsibility Principle (1 link)
- Managing change (1 link)
- Continuous obsolescence (1 link)
- Repository pattern (1 link)
- Model view controller pattern (1 link)
- Minimise class collaborations (1 link)
- Coarse grained lock pattern (1 link)
- GoF (1 link)
- Ron Jeffries (1 link)
- Rule of three (1 link)
- Agile Manifesto (1 link)
- Long method name smell (1 link)
- Mapper pattern (1 link)
- Blackboard pattern (1 link)
- Attribute your sources (1 link)
- Template:Pp-template (1 link)
- Managing functionality (1 link)
- Design by committee (1 link)
- Separated interface pattern (1 link)
- Pipes and filters pattern (1 link)
- Minimise method collaborations (1 link)
- Equals idiom (1 link)
- Concrete table inheritance pattern (1 link)
- Head First Design Patterns (1 link)
- Constructor (1 link)
- Communication diagram (1 link)
- Model-view-controller (1 link)
- Metadata mapping pattern (1 link)
- Broker pattern (1 link)
- God Class (1 link)
- Datamart (1 link)
- Managing performance (1 link)
- Golden hammer (1 link)
- Serialized lob pattern (1 link)
- Presentation abstraction control pattern (1 link)
- Minimise methods between collaborators (1 link)
