Embed Size (px)
Citation preview
www.twitter.com/JorgeCastilloPr
www.github.com/JorgeCastilloPrz
The Developer Journey
Jorge Castillo Pablo Guardiolawww.twitter.com/guardiola31337
www.github.com/Guardiola31337
1Before the
Code
Meetings
Efficiency● Prepare the meeting
● Action points
● Number of people involved
Product definition
Feedback● MVP & Iterations
● Product transparency
“
Work with a user to think like a user
PM education
● Estimations will be required
● User Story definition
Estimation● Avoid hot estimations
● It’s your responsibility to work on them
● Estimations are not deadlines
Define contracts
● Discuss with involved people
● Coordination importance
2During the
Code
Professionalism
Accountability
Communication● Efficient on dailies
● Centralize and persist information
● Be polite
Code
Don’t fear change
● Boy scouting
● Proactiveness
Balance
● Perfect software doesn’t exist
● Working software is not enough
Ownership
● Learn to criticize and to be criticized
● Collective mindset
Tooling● Master (IDE, Shell, shortcuts…)
● Create (libraries, scripts…)
● Automatize
Testing
● Be clever
● Design testable code
● Test state instead of behavior
Feel safe
● Find bugs once
● Test harness for refactoring
● Immediate feedback
CI
“
Test your software or your users will
3After the
Code
● Invest in your knowledge
● Who owns your career?
● Choose who you want to
work with
Conclusions
● Honesty
● Be humble
● Professionalism
● Empathy
● Collective ownership
● Don’t stop learning
● Be an example
● ...
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
Thanks!Any questions?
