Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The Developer Journey Codemotion 2016

The Developer Journey Codemotion 2016

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 previous practice, learning from your co-workers, multidisciplinary teams, teaching to apprentices and having motivation to improve yourself as a professional.

Are you ready to start this journey? Join us!

Pablo Guardiola

November 19, 2016
Tweet

More Decks by Pablo Guardiola

Other Decks in Programming

Transcript

  1. www.twitter.com/JorgeCastilloPr
    www.github.com/JorgeCastilloPrz
    [email protected]
    The Developer Journey
    Jorge Castillo Pablo Guardiola
    www.twitter.com/guardiola31337
    www.github.com/Guardiola31337
    [email protected]

    View full-size slide

  2. 1
    Before the
    Code

    View full-size slide

  3. Efficiency
    ● Prepare the meeting
    ● Action points
    ● Number of people involved

    View full-size slide

  4. Product
    definition

    View full-size slide

  5. Feedback
    ● MVP & Iterations
    ● Product transparency

    View full-size slide


  6. Work with a user to think
    like a user

    View full-size slide

  7. PM education
    ● Estimations will be required
    ● User Story definition

    View full-size slide

  8. Estimation
    ● Avoid hot estimations
    ● It’s your responsibility to work on them
    ● Estimations are not deadlines

    View full-size slide

  9. Define contracts
    ● Discuss with involved people
    ● Coordination importance

    View full-size slide

  10. 2
    During the
    Code

    View full-size slide

  11. Professionalism

    View full-size slide

  12. Accountability

    View full-size slide

  13. Communication
    ● Efficient on dailies
    ● Centralize and persist information
    ● Be polite

    View full-size slide

  14. Don’t fear change
    ● Boy scouting
    ● Proactiveness

    View full-size slide

  15. Balance
    ● Perfect software doesn’t exist
    ● Working software is not enough

    View full-size slide

  16. Ownership
    ● Learn to criticize and to be criticized
    ● Collective mindset

    View full-size slide

  17. Tooling
    ● Master (IDE, Shell, shortcuts…)
    ● Create (libraries, scripts…)
    ● Automatize

    View full-size slide

  18. ● Be clever
    ● Design testable code
    ● Test state instead of behavior

    View full-size slide

  19. Feel safe
    ● Find bugs once
    ● Test harness for refactoring
    ● Immediate feedback

    View full-size slide


  20. Test your software or your
    users will

    View full-size slide

  21. 3
    After the
    Code

    View full-size slide

  22. ● Invest in your knowledge
    ● Who owns your career?
    ● Choose who you want to
    work with

    View full-size slide

  23. ● Honesty
    ● Be humble
    ● Professionalism
    ● Empathy
    ● Collective ownership
    ● Don’t stop learning
    ● Be an example
    ● ...

    View full-size slide

  24. 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

    View full-size slide

  25. Thanks!
    Any questions?

    View full-size slide