1. Pair programming
2. Simple design
Simple Design (DS Principle): You Ain't Gonna Need It
UML, Waterfall Development Pattern: Design->Achieving
Good Design helps to cope with changes more easily over time
1. Reversibility
of decisions 2. Technical Agility
Continuous refactoring to adapt to changes
Clean code is easy to maintain and modify
Use tests to drive design
3. Simplicity
focus on current knowledge, reduce waste
Minimum viable design
4. Willing to refactor and improve
excellence, improve skills
What's good code?
Clean Code That Work
SOLID:
The Single Responsibility Principle
is closed to modification and open to extension
Liskov Substitution Principle
Interface Separation Principle
Dependency Inversion Principle
Book: "Agile Development Practices and Patterns"
The main difference between Scrum and Kanban:
Scrum: time box, time is fixed
Kanban: one task ends, the next task moves in