Mob Programming Conference

Sam Backus

Mob Programming

Observations

Rules

Rule:
For an idea to go from someones head into the computer it must go through someone else's hands

Pairing is a skill 

Rule:

When navigating start with intent and only give more details if required 

Intention > Location > Details

No production code without tests

No production code without tests

  • Write no production code except to pass a failing test
  • Write only enough of a test to demonstrate a failure
  • Write only enough production code to pass a test

the law of mobility

  1. Classes can be no longer than one hundred lines of code.

  2. Methods can be no longer than five lines of code.

  3. Pass no more than four parameters into a method. Hash options are parameters.

  4. Controllers can instantiate only one object.

5 rules of OOP

"an ounce of practice is worth more than tons of preaching" ~Gandhi 

No bike shedding: 

try both

then vote and move on

It's in the doing of the work that we discover the work that we must do

Learning to work well together means we have to learn about ourselves 

emotional safety

 

Instead of failing less 

reduce the cost of failure/change

Continuous Learning

 

Retrospectives

turn up the good
 

Satisficing vs. Optimizing

If you system requires discipline, maybe the system is broken

Whiteboard -> English -> Code

Refactoring english is easier than refactoring Code

Mob Programming Conference

By Sam Backus

Mob Programming Conference

  • 261