Code as a Communication Tool

1. Code as a Communication 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

4. About us Vinicius Gomes Mozair • about.me/vvgomes  @MACSkeptic  github.com/macskeptic © ThoughtWorks 2008

6. Introduction © ThoughtWorks 2008

7. Reading existing code is expensive

8. Understanding existing code is expensive

9. Finding out where to change is expensive

10. Maintenance is expensive

11. So, what to do?

13. What? © ThoughtWorks 2008

18. Communicate through code effectively

19. Make it fast to read

20. Make it easy to understand

21. Express domain knowledge through software

22. Keep maintenance costs low

26. Why? © ThoughtWorks 2008

27. Maintenance

28. Tech Debt © ThoughtWorks 2008

29. Time to market vs. Technical debt © ThoughtWorks 2008

30. What we do • XP –Communication –Simplicity –Feedback –Courage –Respect © ThoughtWorks 2008

31. Feedback © ThoughtWorks 2008

32. Feedback Project1 Project2 Unitary Unitary Project1 Project2 Functional Functional Project1 Project2 Regression Regression © ThoughtWorks 2008

33. Help your team

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

39. How? © ThoughtWorks 2008

40. • Language constructs

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. Language constructs

49. © ThoughtWorks 2008

53. Avoid the Comic Sans Effect

58. Tell “what”, not “how”

62. Implementation Patterns

63. Name by role

66. Abiding by the law of Demeter

71. Abstraction symmetry

74. One-line ifs

90. Domain Specific Languages

94. Conclusion

95. Start to think about the code as a communication tool

96. Harness the power of the tools at hand

97. Make the code talk the domain knowledge

98. Write code for human 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. Thanks :)

102. Did you like this subject? Would you like to work with things like that on a daily basis? 05/20/11 © ThoughtWorks 2008

103. Come get to know 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

Code as a Communication Tool

Recommended

Recommended

More Related Content

Similar to Code as a Communication Tool

Similar to Code as a Communication Tool (20)

Code as a Communication Tool