Pair Programming, TDD and Other Impractical Things

Pair Programming, TDD and Other Impractical Things

PHP UK Conference via YouTube Direct link

What is Pair Programming about?

19 of 24

19 of 24

What is Pair Programming about?

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Pair Programming, TDD and Other Impractical Things

Automatically move to the next video in the Classroom when playback concludes

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

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.