The Software Craftsman


Published on

What does the Software Craftsman persona looks like?

Published in: Technology
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

The Software Craftsman

  1. 1. The Software Craftsman<br />Gøran Hansen<br />Aspiring Software Craftsman Senior Consultant @ Capgemini<br /><br /> <br /><br />
  2. 2. Outline<br />Why do we need Software Craftsmen?<br />Characterization of a Software Craftsman<br />Manifesto of Software Craftsmanship<br />How to become a Software Craftsman<br />
  3. 3. Why do we need Software Craftsmen?<br />
  4. 4. “The best processes in the world will not save a project from failure if the people involved do not have the necessary skills to execute the process; conversely, really good developers can make any process work” <br />– Pete McBreen, Software Craftsmanship: The New Imperative<br />
  5. 5. The Total Costofowning a Mess<br />“You have probably been slowed down by messy code. The degree of the slowdown can be significant. Over the span of a year or two, teams that were moving very fast at the beginning of a project can find themselves moving at a snail's pace.”<br />“Over time the mess becomes so big and so deep and so tall, they can not clean it up. There is no way at all”<br />“As the mess builds, the productivity of the team continues to decrease, asymptotically approaching zero. As productivity decreases, management does the only thing they can; they add more staff to the project in hopes of increasing productivity.”<br />“Furthermore, they, and everyone else on the team, are under horrific pressure to increase productivity. So they all make more and more messes, driving the productivity ever further toward zero”<br />- Robert C. Martin, Clean Code<br />
  6. 6. How Scrum Can Fail<br />
  7. 7. “Agilists assume craftsmanship<br />Only few people pursue craftsmanship”<br /><ul><li>JurgenAppelo</li></ul><br />
  8. 8. Why do we need Software Craftsmen…?<br />
  9. 9. … Because crappy code amplify the risk of failure – even for agile projects!<br />
  10. 10. When do we write crappy code?<br />
  11. 11. Pressure<br />
  12. 12. When we have to “Get It Done”!<br />
  13. 13. ”Get It Done”<br />vs.<br />”Get It Right”<br />
  14. 14. An idea<br />
  15. 15. ConstantPressure<br />
  16. 16. Every Week<br />
  17. 17. Pressure<br />
  18. 18. Every Month<br />
  19. 19. Pressure<br />
  20. 20. Every Year<br />
  21. 21. Pressure<br />
  22. 22.
  23. 23. What differentiate between making the choice of “Get It Done” vs. “Get It Right”?<br />
  24. 24. Skill deficiency<br />
  25. 25. A Software Craftsman will choose “Get It Right”<br />
  26. 26. Because he has the skills to do so…<br />
  27. 27. Not only will he “Dot It Right”, he will also do it for the right reasons…<br />
  28. 28. The characterization of a Software Craftsman<br />
  29. 29. He will “Do It Right” – also under pressure<br />
  30. 30. He takes responsibility<br />
  31. 31. He takes pride in his work. Both the end product and the process towards it<br />
  32. 32. He signs his work<br />
  33. 33. “Software Craftsmanship is all about putting responsibility and pride back into the software development process. As Hunt and Thomas (The Pragmatic Programmer) state, we need to start ‘signing our work’ again, just as other craftsmen do” <br />– Pete McBreen, Software Craftsmanship: The New Imperative<br />
  34. 34. He is a continuous learner. When he doesn’t work, he spends his time studying, to find new methods and tools can refine him as a Software Craftsman<br />
  35. 35. “An investment in knowledge always pays the best interest”<br />- Benjamin Franklin<br />
  36. 36. He practice deliberately, and understands the difference between practice and work. He practices in order to be prepared for work<br />
  37. 37. He writes code<br />
  38. 38. “Knowledge is not the same as having the skills and practical ability to create software” <br />– Pete McBreen, Software Craftsmanship: The New Imperative<br />
  39. 39. He has the right attitude towards Software Development<br />
  40. 40. He contribute to the community<br />
  41. 41. Characterization of a Software Craftsman<br />Will “Do It Right”<br />Take responsibility<br />Take pride in his work<br />Signs his work<br />Continuous learner<br />Practice deliberately<br />Write code<br />The right attitude <br />Contribute to the community<br />
  42. 42.
  43. 43. How to become a Software Craftsman…<br />
  44. 44. Tips from The Pragmatic Programmer:<br />Care about your craft<br />Think about your work<br />
  45. 45. Start learning<br />
  46. 46. Take responsibility for your professional career and apply what you’ve learned<br />
  47. 47. Start to Practice<br />Code Dojos<br />Code Katas<br />Pair programming with other fellow Craftsmen<br />
  48. 48. What to practice?<br />TDD – can be applied to all languages<br />Functional, dynamic and statically typed languages – learn the different paradigms<br />Refactoring – learn how to change your code efficiently<br />Design patterns<br />Tools (ReSharper, Visual Studio, Ndepend, Pex etc)<br />Frameworks (Nhibernate, Mongo db etc)<br />
  49. 49. A special thanks to<br />Corey Haines, for letting me using his slides.<br /><br /> <br />
  50. 50. The Software Craftsman<br />Gøran Hansen<br />Aspiring Software Craftsman Senior Consultant @ Capgemini<br /><br /> <br /><br />