Software Craftsmanship Workshop
0 likes161 views
To become really good at anything takes a lot of practice. Apprenticeships and formal mentoring, common in medieval times, are rare today. To create quality code we need solid practices like Test Driven Development and Pair Programming or Mobbing. In this software craftsmanship workshop attendees practiced those skills on in a code kata.
Software Craftsmanship Workshop
- 2. So/ware Cra/smanship cbell@CamilleBellConsul$ng.com 2 ≒ Tradi8onally cra/smen prac8ced a lot ≒ Tradi8onally cra/smen worked under masters, who guided them in their cra/ ≒ Doctors s8ll work as appren8ces under masters in their internships and residencies ≒ But so/ware developers don't have a tradi8on of prac8ce mastering our cra/ ≒ Code Dojos where we prac8ce TDD, Refactoring and Pairing can 鍖ll this gap
- 4. Develop in Baby Steps cbell@CamilleBellConsul$ng.com 4 ≒ Write a 8ny test ≒ Watch it fail ≒ Write only enough code to make it pass - KISS ≒ Watch it pass ≒ If the code gets messy, refactor in baby steps ≒ Repeat
- 5. 3 Rules of Test Driven Development 1. You are not allowed to write any produc8on code unless it is to make a failing unit test pass. 2. You are not allowed to write any more of a unit test than is su鍖cient to fail; and compila8on failures are failures. 3. You are not allowed to write any more produc8on code than is su鍖cient to pass the one failing unit test. With tests you are in control; without tests you arent! Bob Mar8n - The Three Rules of TDD cbell@CamilleBellConsul$ng.com 5
- 8. ≒ Programmers restructure system by improving the design of exis8ng code without changing its behavior to remove duplica8on, improve communica8on, simplify, or add 鍖exibility ≒ Refactoring is not random change, instead its driven by learning from our tests and from iden8fying and 鍖xing code smells ≒ DRY (Dont Repeat Yourself) ≒ Refactoring can occur just prior or just a/er wri8ng new code ≒ Test, code, refactor, re-test Very short cycles refactor in baby steps Refactoring When 鍖xing bugs, write a Red test, BEFORE 鍖xing the bug. Test will run Green when bug 鍖xed. When working with legacy code make sure to write automated tests BEFORE refactoring code, If tests didnt exist. cbell@CamilleBellConsul$ng.com 8
- 10. Mob Programming ≒ Whole team works together ≒ On the same thing ≒ At the same 8me ≒ In the same space ≒ Using the same computer ≒ Driver rotates ≒ Everyone par8cipates ≒ Great for training & prac8ce ≒ Great for collabora8on ≒ Everyone up to speed faster ≒ Some teams mob always, others frequently ≒ Features delivered faster single piece 鍖ow /wo hando鍖s cbell@CamilleBellConsul$ng.com 10 1
- 12. Some Kata References cbell@CamilleBellConsul$ng.com 12 ≒ The Coding Dojo Handbook Available in PDF from Lean Pub hmps://leanpub.com/codingdojohandbook ≒ Search for katas available online (such as): ≒ Bowling Game Kata (Uncle Bob's classic) ≒ Red Pencil Promo8on Kata (Messy Business Rules) ≒ Credit Card Number Validator ≒ Ordered Jobs Kata ≒ and many more