This document discusses techniques for practicing and improving programming skills. It recommends practicing test-driven development, pairing programming, refactoring with all tests passing, and continuous integration. It emphasizes practicing testing contracts and interfaces rather than behavior, and testing programs from the outside-in perspective. The document concludes by encouraging freeing the mind and practicing programming as an art.

1. The practicing programmerTampereGoes AgilesJohannes Brodwall, Just-a-programmerSteriaNorway

2. The Practicing Programmer

3. PracticingProgramming

4. How to workbetterHow to learnbetter

5. Test-firstXP Explained 1stedOn-sitecustomerCISimple design40-hour weekFrequentreleasesCollectiveownershipRefactoringMetaphorCode standardPairingThe planning game

6. Test-firstOn-sitecustomerCISimple design40-hour weekFrequentreleasesCollectiveownershipRefactoringMetaphorCode standardPairingThe planning game

7. Test-firstOn-sitecustomerCISimple design40-hour weekFrequentreleasesCollectiveownershipRefactoringMetaphorCode standardPairingThe planning game

8. Demo

9. Whatdidyousee?

10. Whendidweswitch ”driver”?Effectsofpairing?Howmany tests?Test frequencyIDE tricksStepsize? Toosmall? Toobig?Whendidwerefactor?First test?Pickingnext test?Final test?

11. Test-firstOn-sitecustomerCISimple design40-hour weekFrequentreleasesCollectiveownershipRefactoringMetaphorCode standardPairingThe planning game

12. Whybecomebetter at programming?

13. Seriously. Why?

14. Only 13.37% ofeffort

15. Gettingbetterquality

16. GettingbetterqualityCorrectnessMaintainability

17. But more importantly!

18. Thinkbetter

19. ThinkbetterRaiseyourlevelofabstraction

20. What to practice

21. Test thecontract

22. Test thecontractAPINot behavior

24. Test from outside-in

25. Test from outside-inWho?Why?Pop!Mock

27. TODO: Bilde av standup og tavleKonfidensiell - Navn på presentasjon.ppt17.09.201127

28. Practice pair programming

29. Pingpong

30. Failing testFixthe testFailing testFixthe testFailing test

31. Failing testFixthe testRefactorFailing testFixthe testRefactorFailing test

32. JohannesJussiKatjaAriVlad

33. JohannesJussiKatjaAriVlad

34. JohannesJussiKatjaAriVlad

35. All-greenrefactoring

36. All-greenrefactoringReducethe time ofuncertainty

37. Continuousintegration

38. ContinuousintegrationAvoidbranchingRun tests all the time

40. Pick a demo

41. Pick a demoOutside-inMockingContract testAll-greenrefactoringContinuousintegration

42. How to practice

43. PracticePracticekatasPractice at workPractice in dojos

44. Conclusion

45. ConclusionFreeyourmind

46. FreeyourmindPracticeour art

47. Thankyoujohannes.brodwall@steria.nohttp://johannesbrodwall.comhttp://twitter.com/jhannes