Learning
search
Ctrlk
  • Software Engineering Golden Treasury
  • Trail Map
  • Cachingchevron-right
  • Careerchevron-right
  • Computer Sciencechevron-right
  • devopschevron-right
  • General Paradigmschevron-right
    • CAP theorem
    • designing data-intensive applications summary
    • a-philosophy-of-software-design-notes
    • Aspect oriented Programming (AOP)
    • Best Practice
    • Cargo Cult
    • Clean Code
    • Coding reflections
    • Cognitive Complexity
    • Complexity
    • Conventions
    • Design discussions
    • Design
    • Edge Cases
    • Error Handling Checklist
    • Exceptions
    • Feature Flags/toggle
    • Functional requirements
    • Last Responsible Moment
    • Lock In
    • Named Arguments
    • Naming
    • Performance Fallacy
    • Quality
    • Redesign of a system
    • Resuse vs Decoupling
    • Rules for software designs
    • Sad Paths
    • Scaling Webservices
    • Scientific Method
    • stream-processing
    • Upstream and Downstream
    • Patternschevron-right
    • Architecturechevron-right
    • Design architecture aimschevron-right
    • READMEchevron-right
    • Patterns of Enterprise Application Architecturechevron-right
    • Principleschevron-right
    • programming-typeschevron-right
      • Coding to Contract/Interface
      • Links
      • Declarative vs Imperative Programming Languages
      • defensive-programming
      • Design by contract
      • Domain Specific Languages (DSL)
      • Event Driven
      • file-transfers
      • Logical Programming
      • Mutability
      • Self Healing
      • Simplicity
      • Type Driven Design
      • Value objects
      • Aspect Oriented Programming
      • Concurrent and Parallel Programmingchevron-right
      • Functional Programmingchevron-right
      • oop-designchevron-right
        • Issues with object oriented code
        • Aggregation
        • Anti Patterns
        • Association
        • class-and-objects
        • Composition
        • general-laws-of-programming
        • general-notes
        • Getters and Setters
        • Inside out programming
        • Inversion of control
        • oop-design
        • Other principles
        • Outside in programming
        • Readability
        • Why OO is bad
        • READMEchevron-right
        • clean-codechevron-right
      • Reactive Programmingchevron-right
    • Projects and Software typeschevron-right
    • State Machineschevron-right
  • Otherchevron-right
  • Hardwarechevron-right
  • Integrationchevron-right
  • Languageschevron-right
  • Management & Workflowchevron-right
  • Networkschevron-right
  • Operating Systemschevron-right
  • Other Topicschevron-right
  • persistancechevron-right
  • Securitychevron-right
  • Testing, Maintainablity & Debuggingchevron-right
  • Version Control - Gitchevron-right
  • aichevron-right
gitbookPowered by GitBook
block-quoteOn this pagechevron-down
  1. General Paradigmschevron-right
  2. programming-typeschevron-right
  3. oop-design

class-and-objects

  • https://www.yegor256.com/2014/11/20/seven-virtues-of-good-object.htmlarrow-up-right

hashtag
naming

  • https://www.yegor256.com/2015/03/09/objects-end-with-er.htmlarrow-up-right

PreviousAssociationchevron-leftNextCompositionchevron-right

Last updated 6 years ago

Was this helpful?

Was this helpful?