The document discusses concepts related to software craftsmanship including agile development practices, testing approaches like test-driven development, clean code principles, and professional development. It emphasizes the importance of continuously learning, practicing skills like automated testing, and owning one's career through activities like practicing code reviews and learning from books on software craftsmanship.

1. ColdFusion Craftsmanship
Kev McCabe
Agile Coach & Code Smith
Red Giraffes
ColdFusion Summit 2016
Monday 10th October 2016 1

2. 2

3. Agile Software Development
We are uncovering better ways of developing software by doing it and
helping others do it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
3

4. The invisible threat
Code
quality
Time per
feature
4

5. Manifesto for Software Craftsmanship
raising the bar
As aspiring Software Craftsmen we are raising the bar of professional software
development by practising it and helping others learn the craft. Through this
work we have come to value:
Not only working software,
but also well-crafted software
Not only responding to change,
but also steadily adding value
Not only individuals and interactions,
but also a community of professionals
Not only customer collaboration,
but also productive partnerships
5

6. What is Software Craftsmanship?
Software Craftsmanship is all about putting
responsibility, professionalism, pragmatism and
pride back into software development
6

7. 7

8. Adding value through practice
Automated testing
Test first
Test-Driven Development
Pair-programming
Continuous Integration
8

9. Mastering the practices is hard …
… and that's why we practice
9

10. Perfect practice
(narrowing the gap)
10

11. Software Craftsmanship Attitude
Owning your career
Not a 9 to 5 Profession
Practice
Boy Scout Rule
Expecting Promotions
11

12. Keep Learning
Learn stuff all the time
Small and often
You don’t want to be out of work and having a
large learn curve
Learning is remembering what is important
12

13. Big Learning Curve
13

14. Small and Often
14

15. 15
From Introducing Delivery Mapping
by Chris Matts & Dan North

16. 16
From Introducing Delivery Mapping
by Chris Matts & Dan North

17. 17
From Introducing Delivery Mapping
by Chris Matts & Dan North

18. 18
From Introducing Delivery Mapping
by Chris Matts & Dan North

19. 19
From Introducing Delivery Mapping
by Chris Matts & Dan North

20. 20
From Introducing Delivery Mapping
by Chris Matts & Dan North

21. 21
From Introducing Delivery Mapping
by Chris Matts & Dan North

22. 22
From Introducing Delivery Mapping
by Chris Matts & Dan North

23. People Liquidity
Don’t be an i shaped person
be a T shaped person
or even better a M shaped person
23

24. Seniority is subjective and transient
24

25. The attitude towards legacy code
25

26. Why would we want to be
better developers?
26

27. Craftsmanship is not enough to guarantee
the success of a project but the lack of it can
be the main cause of its failure
27

28. Agile and Craftsmanship complement each other and
both are necessary.
Agile processes assume technical excellence and a
professional attitude.
Software Craftsmanship takes technical excellence and
professionalism to a whole new level.
28

29. Clean Code
Meaningful Names
Short Functions
▪ Single Responsibility Principal
▪ Minimal Arguments
Show intent
▪ No need for comments
Formatting
Unit Testing
29

30. Comments
Inappropriate Information
Obsolete Comment
Redundant Comment
Poorly Written comments
Commented-Out Code
30

31. Functions
Too Many Arguments
Flag Arguments
Dead Functions
Do one thing and one thing only
31

32. Names
Choose Descriptive Names
Long names for long scopes
Avoid Encodings
32

33. General
Multiple languages in files
Obvious Behaviour Is Unimplemented
Duplication
Duplication
Vertical Separation
Inconsistency
Magic Numbers
33

34. General
Positive Conditions
Encapsulate Conditions
34

35. Code Reviews
35

36. Code Layout Matters
Easy to scan
Expressive layout
Compact format
Code is written once and Read ∞
36

37. 37

38. How do we know we are building the
right thing?
How do we know we are building the
thing right?
38

39. Testing
TDD – Test Driven Development
BDD – Behaviour Driven Development
▪ AKA: Acceptance Testing / Specification by Example
39

40. TDD – Test Driven Development
40
Growing Object-Oriented Software, Guided by Tests
by Steve Freeman & Nat Pryce

41. BDD – Behaviour Driven Development
41
Growing Object-Oriented Software, Guided by Tests
by Steve Freeman & Nat Pryce

42. 42

43. The Elements of Programming Style
1st edition 1974
2nd edition 1978
56 lessons
Most of which are still
valid today
43

44. Some of the rules valid today
1. Write clearly -- don't be too clever.
2. Say what you mean, simply and directly.
3. Write clearly -- don't sacrifice clarity for
efficiency.
4. Replace repetitive expressions by calls to
common functions.
5. Parenthesize to avoid ambiguity.
6. Choose variable names that won't be
confused.
7. Write first in easy-to-understand pseudo
language; then translate into whatever
language you have to use.
8. Don't patch bad code -- rewrite it.
9. Write and test a big program in small pieces.
10. Check some answers by hand
11. Make it fail-safe before you make it faster.
12. Make it clear before you make it faster.
13. Don't sacrifice clarity for small gains in
efficiency.
14. Don't strain to re-use code; reorganize
instead.
15. Make sure special cases are truly special.
16. Don't just echo the code with comments --
make every comment count.
17. Don't comment bad code -- rewrite it.
18. Use variable names that mean something.
19. Format a program to help the reader
understand it.
20. Don't over-comment.
44

45. 45

46. Maturity
46

48. Books
Written By Sandro
Part of the Robert C. Martin
Series (Uncle Bob)
Out Just before Christmas
ISBN-10: 0134052501
48

49. Clean Code
Robert “Uncle Bob”
Martin
Changes your thought
process
+ Videos
Also Clean Coders – More
about your career
49

50. Extreme Programming
Explained: Embrace
Change
Kent Back
Good Technical
Practices
50

51. Working Effectively
with Legacy Code
Michael Feathers
51

52. Growing Object-
Oriented Software,
Guided by Tests
Steve Freeman
Nat Pryce
52

53. Your Career
You own It!
You got to work for it
You can never stop
53

54. Questions
54