Software as a craft

¿Has leído algún libro sobre nuestra profesión? No, es que se quedan obsoletos enseguida. ¿Nuestra profesión sólo trata de saber programar en uno u otro lenguaje? ¿De conocer una u otra tecnología? En esta charla reflexionaremos sobre nuestra profesión y cómo poder ser un poquito más felices ;)

Transcript

1. @bberrycarmen @codurance_ES Software as a craft #DevFestTarragona @GDGTarragona
2. Thanks ...
3. THANKS ... @codurance_ES @verologu @VanessaGaRe @GDGTarragona
5. Once upon a time ...
9. … the (pure) WaterFall method is arrogant in its confidence: ... requirements phase, we will identify all relevant requirements, and correctly ... analysis and design phases, we will interpret the requirements correctly, and produce an implementable architecture and design which will not need changes. ... coding phase, we will interpret the design correctly and make no significant mistakes ... testing phase, we will test correctly, and (sufficiently) exhaustively wiki.c2.com Ward Cunningham
10. Requirements Analysis Design Coding Testing Lack of practice Distance between master and apprentice Difficulty in giving feedback Don’t think Lack of humility Deployment Separation
11. Requirements Analysis Design Coding Testing Spikes Master and apprentice together Everybody thinks Humility Deployment Continuous integration, deployment and delivery Fast feedback No separation between coding and quality Evolutionary design Postponed decisions
12. Manifesto for Software Craftsmanship Raising the bar. As aspiring Software Craftsmen we are raising the bar of professional software development by practicing it and helping others learn the craft.
13. Two pillars - Practice -
14. Two pillars - Practice - Master/apprentice relationship
15. Two pillars - Practice - Master/apprentice relationship
18. Coderetreat Coderetreat is a volunteer-based, globally coordinated effort to improve software developer's skills. http://coderetreat.org @coderetreat
21. DRIVER NAVIGATOR
22. Pair programming - Respect - ‘Let’s try your idea first’ - DRIVER: Thinking out loud - NAVIGATOR: 10-second rule - Don’t worry if it feels awkward at first
23. Evolutionary design?
24. A design discipline: Test-Driven Development (TDD)
25. @KentBeck
26. PRODUCTION CODE TEST CODE Implementation
27. TEST CODE PRODUCTION CODE Behaviour/Intention
28. WRITE TEST CODE WRITE PRODUCTION CODE REFACTOR
29. Refactor ?
30. Production code & Test code
31. 4 RULES OF SIMPLE DESIGN
32. “Design for the future. Change is expensive. Make it cheap by anticipating it.”
33. 4 RULES OF SIMPLE DESIGN • Pass all the tests • Reveal intention • No duplication • Fewer elements
34. 4 RULES OF SIMPLE DESIGN • Pass all the tests • Reveal intention • No knowledge duplication • Fewer elements
35. 4RSD Clean architecture Connascence S.o.C. Cohesion Coupling P.O.L.A. D.R.Y. GoF Patterns K.I.S.S. Y.A.G.N.I. Law of Demeter S.O.L.I.D. DDD Screaming Architecture
36. WRITE TEST CODE WRITE PRODUCTION CODE REFACTOR HUMILITY
38. A side benefit: coverage
41. Two pillars - Practice - Master/apprentice relationship
44. https://softwarecrafters.slack.com
45. SoCraTes Software Craftsmanship retreat for open-minded craftspeople who want to improve their craft.
49. Not only reading ...
50. I love... • About the author • Preface • Foreword • Acknowledgements
52. Learning culture at your work • Brown bag lunch • Lunch & Learn • Book club • ...
53. Master is also apprentice
55. @codurance_ES @bberrycarmen