The Developer Journey

In our daily lives as a developers, testers, release engineers, or other disciplines, we are always pursuing to create the best code as possible but always responding to our customers without taking into account the quality of the code we are delivering. Creating good software is not possible without meeting efficiency, good estimation, previous practice, learning from your co-workers, multidisciplinary teams, teaching to apprentices and having motivation to improve yourself as a professional.

Transcript

1. www.twitter.com/JorgeCastilloPr www.github.com/JorgeCastilloPrz jorge.castillo.prz@gmail.com The Developer Journey Jorge Castillo Pablo Guardiola www.twitter.com/guardiola31337 www.github.com/Guardiola31337 guardiola31337@gmail.com
2. 1 Before the Code
3. Meetings
4. Efficiency • Prepare the meeting • Action points • Number of people involved
5. Product definition
6. Feedback • MVP & Iterations • Product transparency
7. “ Work with a user to think like a user
8. PM education • Estimations will be required • User Story definition
9. Estimation • Avoid hot estimations • It’s your responsibility to work on them • Estimations are not deadlines
10. Define contracts • Discuss with involved people • Coordination importance
11. 2 During the Code
12. Professionalism
13. Accountability
14. Communication • Efficient on dailies • Centralize and persist information • Be polite
15. Code
16. Don’t fear change • Boy scouting • Proactiveness
17. Balance • Perfect software doesn’t exist • Working software is not enough
18. Ownership • Learn to criticize and to be criticized • Collective mindset
19. Tooling • Master (IDE, Shell, shortcuts…) • Create (libraries, scripts…) • Automatize
20. Testing
21. • Be clever • Design testable code • Test state instead of behavior
22. Feel safe • Find bugs once • Test harness for refactoring • Immediate feedback
23. CI
24. “ Test your software or your users will
25. 3 After the Code
26. • Invest in your knowledge • Who owns your career? • Choose who you want to work with
27. Conclusions
28. • Honesty • Be humble • Professionalism • Empathy • Collective ownership • Don’t stop learning • Be an example • ...
29. Bibliography • Pragmatic programer • The Software Craftsmanship • Clean code • Working Effectively with Unit Tests • Refactoring: Improving the design of existing code • Debugging Teams • Presentation template by SlidesCarnival
30. Thanks! Any questions?