Principles

Recent Principles

• Many minds, better problem-solving

  The greater the number of people who can work on a problem, the higher the probability of an optimal solution.

  • medium
  • problem-solving
  • practices
  • team

  Adam Craven

• Relatedness pattern

  Things that are related to one another and ordered logically do not increase cognitive complexity

  • code
  • individual
  • comprehension
  • cognitive
  • focused

  Adam Craven

• Principle of evolvability

  Systems which can evolve quicker are better than those which cannot.

  • core
  • mental model
  • epic
  • basic

  Adam Craven

• Go wide, then refine

  When creating something, it is better to understand the picture - at a high level - instead of focusing on the thing you need to create immediately.

  • practices
  • team
  • medium
  • domain
  • ddd
  • epic
  • leadership

  Adam Craven

• Code should work, but does not have to be efficient.

  • code
  • team
  • medium
  • performance
  • phase
  • sdlc
  • mvp

  Adam Craven

• Be constructive, not destructive.

  • practice
  • medium
  • team
  • leadership

  nickyhannaway

• When you know you aren’t aligned, resolve early.

  Act on unalignment rapidly to ensure happy teams

  • medium
  • leadership
  • practices
  • team

  Adam Craven

• Understand a problem individually, then share it.

  Capture your understandings separately to the team and then come together to align

  • team
  • process
  • medium
  • comprehension
  • remote-work

  

• Hollywood Principle

  Write code to respond to external events, such as from an existing framework

  • code
  • organization
  • rdt
  • team

• Dependency Inversion Principle

  high level modules should not depend on low level modules; both should depend on abstractions.

  • code
  • practices
  • team
  • organization
  • rdt
  • solid

• Explicit Dependencies Principle

  Methods and classes should explicitly require any collaborating objects they need in order to function correctly

  • code
  • organization
  • rdt
  • team

• Test models thoroughly, test everything else less

  • bug free
  • front-end
  • practices

  Adam Craven

• Model all state in an application

  Create a structured representation of the system's state

  • bug free
  • front-end
  • practices

  Adam Craven

• Ensure UI components can be loaded separately from an application

  • bug free
  • front-end
  • practices

  Adam Craven

• Single-Responsibility Principle

  Every module, class or function in a computer program should have responsibility over a single part of that program's functionality, and it should encapsulate that part

  • code
  • practices
  • team
  • organization
  • solid

  Robert C. Martin

• Try to delete the part or process.

  Try to delete the feature or process to build things that are required.

  • organization
  • strategic
  • leadership
  • epic

  Elon Musk

• Keep It Simple Stupid (KISS)

  A simple solution is better than a complex one.

  • code
  • team
  • epic

• Musk requirement principle

  Requirements belong to individuals, not teams

  • organization
  • strategic
  • leadership
  • epic

  Elon Musk

• Murphy's law

  Whatever can go wrong will go wrong. So a solution is better the fewer possibilities there are for something to go wrong.

  • strategic
  • epic

• Use default arguments instead of short circuiting or conditionals

  • variables
  • rule
  • code
  • clean code
  • code review