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

Code Trails

Code Trails

Talk given at Paris.rb about seeing code as trail signs for future developers.

Martin Van Aken

March 04, 2014
Tweet

More Decks by Martin Van Aken

Other Decks in Programming

Transcript

  1. Code Signs
    Code as a Trail

    View Slide

  2. About.me
    ● Co-founder at 8th color
    ● http://pullreview.com
    ● @martinvanaken
    ● blog.8thcolor.com (Ruby, Code Reviews)
    Learning, reading, laughing

    View Slide

  3. Martin: J’ai une idée de petit talk, intéressé?
    Sylvain: Toujours, le CFP permanent est là
    Martin: Chouette, soumis.

    Martin: Tiens, quand/comment faites-vous la sélection?
    Sylvain: Pas besoin. De facto pour le prochain :)
    Martin: Et le prochain c’est… Mardi. Ah. Bon, je vais
    prendre mes billets de train.

    View Slide

  4. What is code?

    View Slide

  5. View Slide

  6. View Slide

  7. View Slide

  8. Another vision

    View Slide

  9. View Slide

  10. View Slide

  11. Why?

    View Slide

  12. You’ll need to get back
    Maintenance: up to 80%

    View Slide

  13. Other people will need to get
    back
    You Are Not Alone

    View Slide

  14. It will be at night

    View Slide

  15. View Slide

  16. It will rain

    View Slide

  17. View Slide

  18. The trail will be old

    View Slide

  19. View Slide

  20. Avoid being misleading

    View Slide

  21. View Slide

  22. Misleading names

    View Slide

  23. Misleading comments

    View Slide

  24. Dead code

    View Slide

  25. Drop your stones

    View Slide

  26. Name things

    View Slide

  27. Name things

    View Slide

  28. Name things

    View Slide

  29. Put code where it belongs

    View Slide

  30. Put code where it belongs

    View Slide

  31. Put code where it belongs

    View Slide

  32. Be stylish

    View Slide

  33. Be stylish

    View Slide

  34. Avoid complexity

    View Slide

  35. View Slide

  36. View Slide

  37. Test your trail

    View Slide

  38. Test your trail
    Q: How to know if your code is readable?

    View Slide

  39. Test your trail
    A: Read it yourself
    A: Have it read by someone
    → Code Reviews

    View Slide

  40. Always code as if the guy who
    ends up maintaining your
    code will be a violent
    psychopath who knows where
    you live

    View Slide

  41. Code for Humans

    View Slide

  42. Thanks for us!

    View Slide