Object-Oriented Design in Ruby

dependencies.md

# Dependency Management


## Dependency

 * Should be exposed explicitly
 * Should be isolated
 * Should be exposed in an own method

## Interaction Between Objects/Interfaces

 * Objects should be as loosely coupled as possbile
 * Objects should have to know as less as possbile about other objects
 * Build on less likely to change dependencies first

## Arguments

 * Avoid order
 * Try to use hashes
 * Use clear names for keys
 * Handle defaults

single_responsibility.md

Single Responsibility

Class

• Should do the smallest thing possible
• Should be described by a noun
• What it does should be intuitively linked to its name
• Should be small
• Should be easy to reuse

Method

• Should have a single responsibility
• Should be short
• Should be reusable

Variables

• Hide instance variables
• Use attr_accessor etc.

Data

• Hide structure
• Use Struct or a new class to represent data if it make sense