Pair Programming, TDD and Other Impractical Things

Explore efficiency versus effectiveness in software development through this conference talk from PHP UK Conference 2013. Delve into the benefits of "impractical" practices like Test-Driven Development (TDD) and pair programming. Learn how to focus on quality over schedule, ensure both inner and outer quality in projects, and understand the principles of improvement in coding practices. Discover techniques for creating effective project missions, automating acceptance tests, and involving customers in the development process. Gain insights on refactoring, code katas, and the importance of collaborative coding. Challenge traditional notions of efficiency and learn how seemingly impractical methods can lead to more effective software development outcomes.

Syllabus

Intro
coding is not as hard as collaborating
Listen to your customer
First create a project mission based on business goals..
Test Driven Development
impractical
most of the cost in software comes from feedback delay
1. All tests run and pass 2. Remove duplication 3. Remove opacity 4. Remove complexity
THE CODE IS TERRIBLE!! WE NEED ONE SPRINT TO REFACTOR
There is no refactoring without tests There is no testing without refactoring
refactoring === design
Focus on Quality over Schedule
But what causes poor Outer Quality?
Lack of automated acceptance tests Lack of customer involvement Team not focused on Project Mission Lack of Inner Quality
How do you ensure Outer Quality?
Example workshops Automate acceptance tests Have a sprint vision statement Sign off during Sprint
How do you ensure Inner Quality?
2 developers sharing a screen working on the same task
What is Pair Programming about?
Jon Jagger's Principles of Improvement
Pair programming is about improving faster
Strengthening the case for pair programming
Should pairs be kept together?
Code Katas