Pages without language links
From CSSEMediaWiki
Showing below up to 500 results starting with #51.
View (previous 500 | next 500) (20 | 50 | 100 | 250 | 500)
- Avoid downcasting
- Avoid equals
- Avoid god classes
- Avoid inheritance for implementation
- Avoid inheritance for optional containment
- Avoid interface bloat
- Avoid interface pollution
- Avoid mixing inputs and outputs
- Avoid multiple inheritance
- Avoid no-op overrides
- Avoid protected data
- Avoid side effects
- Avoid verb classes
- Barbara Liskov
- BaseBean
- Becomes problem
- Behavioral completeness
- Benjamin's Design Study
- BenjaminTaylor Previous Design Work
- Bertrand's Design Study
- Bertrand Meyer
- Beware accessors
- Beware inheritance over composition
- Beware of many accessors
- Beware of non-communicating methods
- Beware singletons
- Beware type switches
- Beware value switches
- Big ball of mud
- Big design up front
- Blackboard System
- Boat anchor
- Bob Martin
- Bob Martin's heuristics
- Bob Martin's principles
- BrettWardsDesignStudy
- Bridge
- Builder
- CLU
- Call super
- Cay Horstmann 2006
- Chain of Responsibility
- Change Reference to Value
- Change Unidirectional Association to Bidirectional
- Change Value to Reference
- Christopher Alexander
- Christopher Alexander 1977
- Christopher Alexander 1979
- Circle-ellipse problem
- Circular dependency
- Citation needed
- Class Encapsulation
- Class diagram
- Class hierarchies should be deep and narrow
- Class versus Object
- Code smells
- Collapse Hierarchy
- Collecting Parameter
- Combining design patterns
- Command
- Command query separation
- Comments and suggestions
- Comments smell
- Common closure principle
- Common reuse principle
- Component versus Module
- Composite
- Constant interface
- Contain contents not parents
- Contained objects should not use each other
- Containment implies uses
- Copy Constructor vs the Encapsulation Boundary
- Coupling and cohesion
- Cut and paste programming
- DMA Design Project
- DMA Design Project - Source Code
- DMA Design Project - first submission
- DMA Design Project first draft
- Data class smell
- Data clumps smell
- Data mapper pattern
- David Parnas
- Decomposition
- Decorator
- Defer identification of state variables pattern
- Define classes by behavior, not state pattern
- Define default values via explicit protocol pattern
- Delegation
- Dependency injection
- Dependency inversion principle
- Design Project
- Design by contract
- Design examples
- Design maxims
- Design maxims Equivalence
- Design patterns
- Design patterns break rules
- Designfest
- Diamond Problem
- Different Design
- Distribute system intelligence
- Divergent change smell
- Do not change the state of an object without going through its public interface
- Do the simplest thing that could possibly work
- Documenting Patterns
- Domain model pattern
- Don't burn your base class
- Don't expose mutable attributes
- Don't repeat yourself
- Double Dispatch
- Duplicate Observed Data
- Duplicate code smell
- Editing Tips
- Eliminate case analysis
- Eliminate irrelevant classes
- Empty method over-rides
- Encapsulate Collection
- Encapsulate Downcast
- Encapsulate Field
- Encapsulate concrete state pattern
- Encapsulate that which varies
- Encapsulation
- Encapsulation boundary
- Encapsulation is hierarchical
- Enum idiom
- Equals vs the Encapsulation Boundary
- Erich Gamma
- Establishing priorities
- Exam Quick Reference
- Exam questions
- Extensibility
- Extract Class
- Extract Hierarchy
- Extract Interface
- Extract Method
- Extract Subclass
- Extract Superclass
- Extreme programming
- Facade
- Factor implementation differences into subcomponents
- Factory Method
- Fat interfaces
- Favor composition over inheritance
- Favour containment over association
- Favour deep hierarchies
- Feature envy smell
- Flyweight
- Frogs design
- Frogs second design
- Front controller pattern
- Functional decomposition
- Gang of Four
- Gang of Four 1995
- GenA: A Genetic Algorithms Framework
- GenericGuidelines
- Getter and setter policy
- Getters and setters
- God object
- Goto considered harmful
- Greg Searle's captains log star date
- Greg Searle's design
- Greg Searle's project blackjack
- Guitar Amplifier Design
- Guitar Tutor Design
- Guitar Tutor Report
- Hall of fame
- Have courage
- Hide Delegate
- Hide Method
- Hide data within its class
- Hide your decisions
- Hierarchical Model View Controller
- Hillside Group
- HistoryCrumbs.user.js
- How to assess
- Identify message layers pattern
- Identity map pattern
- Idioms
- If it ain't broke don't fix it
- Immutable object
- Impedance mismatch
- Implement behavior with abstract state pattern
- Inappropriate intimacy smell
- Incomplete library class smell
- Information hiding
- Inheritance
- Inheritance for specialization
- Inline Class
- Inline Method
- Inline Temp
- Instance
- Intelligent children pattern
- Interface
- Interface segregation principle
- Interface should be dependent on model
- Interpreter
- Introduce Explaining Variable
- Introduce Foreign Method
- Introduce Local Extension
- Introduce Null Object
- Introduce Parameter Object
- Introduce common base class
- Introduce common data class
- Introduction to the Terrain Renderer
- Inventory and Accounting
- Inversion of control
- Iterator
- JITAS Design Study
- JUnit
- James Ashford Design Study
- James Ashford Log
- Janina's Design Study
- Jason's Useful Links Page
- Java Collections Framework
- Jenny Harlow
- Jim Coplien
- Joey's design study
- Joff's Place
- John Hofman's Design Study
- John Hofman's Log
- John Hofman US001
- Johnson and Foote's heuristics
- Johnson and Foote 1988
- Jojo's 2008 Design Study
- Jojo's OO Design Project Log
- Joshua Bloch
- Joshua Bloch 2006 Bumper Sticker API Design
- Jumble
- Keep accessors and mutators separate
- Keep last years stuff
- Keep related data and behavior in one place
- Ken Auer
- Ken Auer 1995
- Kent Beck
- Kent Beck 2003
- Kris's Design Study
- Language Spectrum
- Large class smell
- Law of Demeter
- Law of leaky abstractions
- Lazy class smell
- Lazy load pattern
- Lecture sequence
- Lecture times
- Limit compositions in a class
- Limit hierarchy depth
- Liskov substitution principle
- List of OO Languages
- Long method smell
- Long parameter list smell
- LukasKorsikaDesignStudy
- Main Page
- Make all Member Variables Private
- Make constructors blocking
- Management antipatterns
- Managing complexity
- Many to many association idiom
- Martin Doms' Design Study
- Martin Fowler
- Martin Fowler 1997
- Martin Fowler 1999
- Martin Fowler 2003
- Martins Design Study
- Matthew's Design Study
- Maxim Hierarchy
- Mediator
- Memento
- Message chain smell
- Method
- Methods should use most fields of a class
- Michael's Design Study
- Michael's Log
- Michal's Design Study
- Middle man smell
- Mike's Design Study
- Minimal public interface
- Minimize accesses to variables
- Minimize number of methods
- Mock objects
- Model classes not roles
- Model the real world
- Model the room
- Model view controller
- Monsters design
- Move Field
- Move Method
- Move common factors up the hierarchy
- Move methods
- Mujtaba's Initial Design
- Mujtaba's Log
- Mujtaba's design study
- Multiple Inheritance
- My actual Project, I think.
- Named constants
- Nelson Shaw Design Project
- Nelson Shaw Project Log
- Nick's Design Study
- Nick Brettel's eight puzzle design
- Nil or export coupling only
- No Global Variables
- No Peter Pan objects
- No silver bullet
- Nomenclature
- OOTetris Design
- OO Python Character Animation Design Study
- OO culture
- OO gurus
- OO tools
- OO wisdom
- Object-oriented design anti-patterns
- Object Encapsulation
- Object cesspool
- Object orgy
- Object pool
- Observations and Measurements
- Observer
- Oliver Cardwell/Project
- Once and only once
- One Into Many
- One hour tour
- One key abstraction
- Open closed principle
- Option-operand separation
- Organisational patterns
- Orthogonality
- Overloading
- PLoP
- PLoP (Software Patterns Series)
- PLoP 1995
- Package versus Namespace
- Page controller pattern
- Parallel hierarchies problem
- Parallel inheritance hierarchies smell
- Parameterise Method
- Parse tree design
- Party of Five 1996
- Party of five 1996
- Patterns
- PaulDesignStudy
- Peer To Peer
- Perfect OO Language
- PluS XML format
- Poker Simulator Design Log
- Poker Simulator Design Writeup
- Poltergeists
- Polymorphism
- Premature optimization
- Presentation Abstraction Control
- Presentation separation idiom
- Preserve Whole Object
- Primitive obsession smell
- Professionalism
- Program to the interface not the implementation
- Project ideas
- Properties
- Properties / Fields / Attributes
- Prototype
- Proxy
- Pull Up Constructor Body
- Pull Up Field
- Pull Up Method
- Push Down Field
- Push Down Method
- Put semantic constraints in class definition
- Put semantic constraints in constructors
- Quick Reference
- Quotes
- RL Design Study Log
- Ralph Johnson
- Real name
- Rebecca Wirfs-Brock
- Rebecca Wirfs-Brock 1990
- Recursion introduction
- Reduce implicit parameter passing
- Reduce the number of arguments
- Reduce the size of methods
- Refactoring
- Refactoring and design
- Refactoring and performance
- Referring to Objects
- Refused bequest smell
- Reinvent the wheel
- Remove Middle Man
- Remove Parameter
- Remove Setting Method
- Remove assignments to Parameters
- Rename Method
- Replace Array with Object
- Replace Conditional with Polymorphism
- Replace Constructor with Factory Method
- Replace Data Value with Object
- Replace Error Code with Exception
- Replace Exception with test
- Replace Inheritance with Delegation
- Replace Magic Number with Symbolic Constant
- Replace Method with Method Object
- Replace Parameter with Explicit Methods
- Replace Parameter with Method
- Replace Temp with Query
- Replace Type Code with Class
- Resources
- Reusable frameworks over reusable components
- Reuse release equivalence principle
- Riel's heuristics
- Robert Cecil Martin 1996a
- Robert Cecil Martin 1996b
- Robert Cecil Martin 1996c
- Robert Cecil Martin 1996d
- Robert Cecil Martin 1996e
- Robert Cecil Martin 1997a
- Robert Cecil Martin 1997b
- Robert Cecil Martin 2002
- Robert Cecil Martin 2003
- Robert Pirsig 1974
- Row data gateway pattern
- Schools of thought
- Scrum
- Self Encapsulate Field
- Send messages to components instead of to self
- Separate Query from Modifier
- Separate methods that do not communicate
- Separate non-communicating behaviour
- Separation of concerns
- Sequential coupling
- Serialization
- Server Requests
- Service layer pattern
- Shallow VS Deep Copy
- Shalloway and Trott 2002
- Shotgun surgery smell
- Sign your work
- Similar patterns and how to tell them apart
- Single choice principle
- Single responsibility principle
- Singleton
- Smalltalk
- Software crisis
- Software reuse
- Sorcerers design
- Spaghetti code
- Speculative generality smell
- Split Temporary Variable
- Split large classes
- Square-rectangle problem
- Stable abstractions principle
- Stable dependencies principle
- Start here
- State
- State machine design
- Stephen's Design Study
- Stovepipe system
- Strategy
- Strategy meets Template
- Subclass
- Subclasses should be specializations
- Substitute Algorithm
- Super quick exam ref
- Superclass
- Swiss army knife
- Switch statement smell
- Table data gateway pattern
- Table module pattern
- Tanmay's Design Study
- Tanmay's Log
- Teaching and learning style
- Tell, don't ask
- Template Method
- Template view pattern
- Temporary field smell
- Terrain Renderer Design
- Test Driven Development
- Text design
- The Alexander conspiracy
- The top of the class hierarchy should be abstract
- Toast
- TobiW's Design Study
- Tour Guide Project Page
- Trains design
- Transaction script pattern
- Transform view pattern
- Trygve Reenskaug
- Unified Modeling Language
- Unit Test
- Unit of work pattern
- Use lazy initialization pattern
- Vehicles and operators design
- Vendor lock-in
- Video rental system
- Visitor
- Wal's Fish Tank
- Wals library
- Ward's wiki
- Ward Cunningham
- Ward and Kent
- Warfarin Design
- What is Bad Design
- Why refactoring works
- Wiki etiquette
- Wiki tips
- Wiki users
