Download as PDF, PPTX
Uploaded byVinicius Gomes
Code as a Communication Tool
This document discusses using code as a communication tool. It recommends writing code that is easy to read and understand through techniques like using language constructs effectively, implementing patterns that clearly communicate roles and abstractions, applying domain-driven design, and using test-driven development and refactoring. The goal is to make code maintenance less expensive by making the code's domain knowledge and intent clear to both current and future developers.
Code as a Communication Tool
- 1. Code as aCommunication Tool AKA Usando as Linguagens ao Seu Favor Vinicius Gomes Mozair May, 23rd 2011 © ThoughtWorks 2008
- 2. Agenda • About us • Introduction • What? • Why? • How? • Conclusion © ThoughtWorks 2008
- 3. Agenda • About us • Introduction • What? • Why? • How? • Conclusion © ThoughtWorks 2008
- 4. About us Vinicius Gomes Mozair • about.me/vvgomes @MACSkeptic github.com/macskeptic © ThoughtWorks 2008
- 5. Agenda • About us • Introduction • What? • Why? • How? • Conclusion © ThoughtWorks 2008
- 6. Introduction © ThoughtWorks 2008
- 7. Reading existing codeis expensive
- 8. Understanding existing code is expensive
- 9. Finding out whereto change is expensive
- 10.
- 11. So, what todo?
- 12. Agenda • About us • Introduction • What? • Why? • How? • Conclusion © ThoughtWorks 2008
- 13.
- 18. Communicate through code effectively
- 19. Make it fastto read
- 20. Make it easyto understand
- 21. Express domain knowledge through software
- 22.
- 25. Agenda • About us • Introduction • What? • Why? • How? • Conclusion © ThoughtWorks 2008
- 26.
- 27.
- 28. Tech Debt ©ThoughtWorks 2008
- 29. Time to marketvs. Technical debt © ThoughtWorks 2008
- 30. What we do •XP –Communication –Simplicity –Feedback –Courage –Respect © ThoughtWorks 2008
- 31.
- 32. Feedback Project1 Project2 Unitary Unitary Project1 Project2 Functional Functional Project1 Project2 Regression Regression © ThoughtWorks 2008
- 33.
- 34. Help your team •Make people more productive
- 35. Help your team •Make people more productive • Avoid ambiguous interpretation
- 36. Help your team •Make people more productive • Avoid ambiguous interpretation • Drop stress levels
- 37. Help your team • Make people more productive • Avoid ambiguous interpretation • Drop stress levels • Help people to focus on the right things
- 38. Agenda • About us • Introduction • What? • Why? • How? • Conclusion © ThoughtWorks 2008
- 39.
- 40.
- 41. • Language constructs •Implementation Patterns
- 42. • Language constructs •Implementation Patterns • Domain Driven Design
- 43. • Language constructs • Implementation Patterns • Domain Driven Design • Test Driven Development / Design
- 44. • Language constructs • Implementation Patterns • Domain Driven Design • Test Driven Development / Design • Refactoring
- 45. • Language constructs • Implementation Patterns • Domain Driven Design • Test Driven Development / Design • Refactoring • Domain Specific Languages
- 46.
- 49.
- 50.
- 51.
- 52.
- 53. Avoid the ComicSans Effect
- 58. Tell “what”, not“how”
- 59.
- 60.
- 61.
- 62. Implementation Patterns
- 63.
- 66. Abiding by thelaw of Demeter
- 71.
- 74.
- 77. Test Driven Design/Development © ThoughtWorks 2008
- 78.
- 79.
- 80.
- 81.
- 82.
- 83. Refactoring © ThoughtWorks 2008
- 84.
- 85.
- 86.
- 87.
- 88.
- 89.
- 90. Domain Specific Languages
- 91.
- 92.
- 93. Agenda • About us • Introduction • What? • Why? • How? • Conclusion © ThoughtWorks 2008
- 94.
- 95. Start to thinkabout the code as a communication tool
- 96. Harness the powerof the tools at hand
- 97. Make the codetalk the domain knowledge
- 98. Write code forhuman beings
- 99. More Information XP Explained by Kent Beck TDD by Example by Kent Beck Implementation Patterns by Kent Beck Refactoring by Martin Fowler Clean Code by Bob Martin Domain Driven Desing by Eric Evans Literate Programming by David Knuth
- 100. about.me/vvgomes @MACSkeptic
- 101.
- 102. Did you likethis subject? Would you like to work with things like that on a daily basis? 05/20/11 © ThoughtWorks 2008
- 103. Come get toknow us, we are looking for smart people interested in doing awesome stuff www.thoughtworks.com/career-opportunities work@thoughtworks.com 05/20/11 © ThoughtWorks 2008