Code Trails

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

Transcript

1. Code Signs Code as a Trail
2. About.me • Co-founder at 8th color • http://pullreview.com • @martinvanaken • blog.8thcolor.com (Ruby, Code Reviews) Learning, reading, laughing
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.
4. What is code?
8. Another vision
11. Why?
12. You’ll need to get back Maintenance: up to 80%
13. Other people will need to get back You Are Not Alone
14. It will be at night
16. It will rain
18. The trail will be old
20. Avoid being misleading
22. Misleading names
23. Misleading comments
24. Dead code
25. Drop your stones
26. Name things
27. Name things
28. Name things
29. Put code where it belongs
30. Put code where it belongs
31. Put code where it belongs
32. Be stylish
33. Be stylish
34. Avoid complexity
37. Test your trail
38. Test your trail Q: How to know if your code is readable?
39. Test your trail A: Read it yourself A: Have it read by someone → Code Reviews
40. Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live
41. Code for Humans
42. Thanks for us!