Development Principles (Software development methodology)

YAGNI (You aren't gonna need it)

  •  do the simplest thing that could possibly work

 KISS (Keep it simple, stupid)


  • Simplicity is the ultimate sophistication

 DRY (Don't repeat yourself)

SOLID Principles:

  •  Introduced by Robert C. Martin in the early 2000s.
  • Helps to create a system that is easy to maintain and extend over time.
  • It is typically used with test-driven development, and is part of an overall strategy of agile and adaptive programming.

  1. Single responsibility principle: the notion that an object should have only a single responsibility.
  2. Open/closed principle: the notion that “software entities … should be open for extension, but closed for modification”.
  3. Liskov substitution principle: the notion that “objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program”.
  4. Interface segregation principle: the notion that “many client specific interfaces are better than one general purpose interface.
  5. Dependency inversion principle: the notion that one should “Depend upon Abstractions. Do not depend upon concretions.”.Dependency injection is one method of following this principle.

Comments

Popular posts from this blog

BDD - Acceptance Test Driven Development

Angular JS – Part 2

.Net Collections