Software Development Principles

principles.md

Don't worry about design, if you listen to your code a good design will appear.

Martin Folwer, Is Design Dead?

Do the simplest thing that could possibly work.

SOLID

1. single responsibility principle

   • a class should have only one reason to change

2. open/closed principle

   • software entities (classes, modules, functions, etc.)
   • should be open for extensions but closed for modification

3. liskow substition principle

   • subtypes must be substitutable for their base types

4. dependency-inversion principle

   • high-level modules should not depend on low-level modules, both should depend on abstraction
   • abstractions should not depend upon details, details should depend upon abstractions

5. interface-segregation principle

KISS

keep it simple, stupid

DRY

don't repeat yourself

YAGNI

you ain't gonna need it