We do 2 week long study iterations. At the end of each iteration we discuss what we have studied in order to align, check if we understand and ask ourselves questions on how to improve our daily work.
- Keep It DRY, Shy, and Tell the Other Guy - Andy Hunt and Dave Thomas
- Integrated Tests Are A Scam - J.B. Rainsberger
- The Four Elements of Simple Design - J.B. Rainsberger
- OOP Principles: Composition vs Inheritance - Dave Crabbe
- Iterative and Incremental Development - Robert Martin
- You Arent Gonna Need It - Ron Jeffries
- Iterative and Incremental Development (IID) - Robert Martin
- 7 minutes, 26 seconds, and the Fundamental Theorem of Agile Software Development - J.B. Rainsberger
- The Cycles of TDD - Robert Martin
- Low Coupling, High Cohesion - Ivan Montiel
- Tennis Refactoring Kata - Emily Bache
- Keynote Italina Agile Day 2010 - Paolo Perrotta
- Refactoring (chapter 2) - Martin Fowler
- Defining Refactoring
- Why should you refactor?
- When should you refactor?
- What do I tell my manager?
- Problems with refactoring
- Refactoring and design
- Refactoring and performance
- Where did refactoring come from?
- Gli schiacciatori NON parlano dell'alzata, la risolvono - Julio Velasco
- Tennis Refactoring Kata - Emily Bache with Calisthenics rules
- One level of indentation per method
- Don’t use the ELSE keyword
- Wrap all primitives and Strings
- First class collections
- One dot per line
- Don’t abbreviate
- Keep all entities small (50 lines)
- No classes with more than two instance variables
- No getters/setters/properties