“Hold, Break, Leave” - First, follow all the practices. - Then, realize and change them. - Finally, you don't need to think about the rules anymore.

1. The Way of
The Software
Craftsman
# Part One: The Beginning
2009, Vitaliy Kulikov

2. Interrupt. Ask questions. Disagree.

3. WHY I CARE

4. Usual Process

5. Beautiful System

6. Add a feature

7. Add a new feature

8. Change a feature

9. Time Passes

10. Look familiar

11. Add a new feature
How?

12. Crap Code

13. Constant Cleaning

14. „Clean code that works“
Ron Jeffries

15. Emergent Design

16. Add a feature

17. Clean It Up

18. Add a new feature

19. Clean It Up

20. Change a feature

21. Time Passes

22. Clean Architecture

23. Over Time

24. How do you do this?

25. USUALLY ...

26. Extreme
Programming
(XP)

27. Development
Techniques

29. Why don’t we do
them?

30. We don’t know how

31. How do you learn to
do it?

32. Emergent Design /
Evolutionary Design

33. Over Time

34. Test-Driven
Development
(TDD)

35. How do we learn?

36. Work != Practice

37. How do we practice?

38. Shu Ha Ri
Shu ( 守 : "protect", "obey" ) - traditional wisdom
Ha ( 破 : "detach", "digress" ) - breaking with tradition
Ri ( 離 : "leave", "separate" ) - transcendence

39. “Hold, Break, Leave”
First, follow all the
practices.
Then, realize and
change them.
Finally, you don't
need to think about
the rules anymore.

40. Testing. Quality. Automation.

41. WHY I CARE (REDUX)

42. „Legacy code is code
without tests“
Michael Feathers

43. The Steps of
test-first design (TFD)

44. TDD = Refactoring + TFD

45. Testing via the xUnit Framework

46. Tests are
documentation
„Every test is an executable example.“

47. Edit and Pray

48. ✗ Carefully plan
✗ Make the change
✗ Start the application
and check the change
✗ Poking around

49. Cover and Modify

50. ✔ Write test
✔ Make the change
✔ Run all tests

51. Tests = Proof

52. If it's worth building,
it's worth testing.
If it's not worth testing,
why are you wasting
your time working on it?

53. ● Another tool for your toolbox
● Use as you need it
● Can be difficult for beginners
● Frameworks can help
TRY IT

54. Tests guide the design
„We see the code from the user‘s perspective“

55. Stop Writing Crap

56. THANK YOU
?

57. ✔ „Test Driven Development by Example“
-Kent Beck
✔ „Working Effectively with Legacy Code“
-Michael Feathers
✔ „Clean Code: A Handbook of Agile
Software Craftsmanship“
-Robert C. Martin
RESOURCES