Pair Programming, TDD and Other Impractical Things
Offered By: PHP UK Conference via YouTube
Course Description
Overview
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
Taught by
PHP UK Conference
Related Courses
Software as a ServiceUniversity of California, Berkeley via Coursera Software Testing
University of Utah via Udacity The Hardware/Software Interface
University of Washington via Coursera Software Debugging
Saarland University via Udacity Introduction to Systematic Program Design - Part 1
The University of British Columbia via Coursera