Tools to help you understand other people's code

1,776 views

Published on

There are 4 main issues, you should be aware of:
1. Class Diagram
2. Gems
3. Test before the change
4. Take care of your team style

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,776
On SlideShare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
7
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • http://rails-erd.rubyforge.org/ https://github.com/preston/railroady
  • https://github.com/sakuro/gem-changelog https://gist.github.com/dpaluy/6855751 http://gemnasium.com/
  • https://github.com/roodi/roodi https://github.com/railsbp/rails_best_practices https://github.com/makaroni4/sandi_meter
  • Tools to help you understand other people's code

    1. 1. Tools to help you better understand other/your code David Paluy, @dpaluy @RailsIsrael2013 Blog: dpaluy.github.io
    2. 2. Agenda ● Working with other people's code ● Class Diagram ● Outdated Gems ● Test before Refactoring ● Style your code
    3. 3. I am a Starter
    4. 4. It doesn't pay my bills, Yet!
    5. 5. Working with Other People's Code
    6. 6. The only valid measurement of code quality: WTFs/minute source
    7. 7. You need tools, to find the needle!
    8. 8. Class Diagram ● Rails ERD ● RailRoady
    9. 9. Gems
    10. 10. bundle outdated
    11. 11. Tracking Gems ● gem-changelog ● changelog_diff (by David Miani) ● gemnasium.com
    12. 12. Test before ...!
    13. 13. Each Developer has his own style?
    14. 14. Check your Style ● roodi ● rails_best_practices ● sandi_meter
    15. 15. Summary
    16. 16. Any fool can write code that a computer can understand. Good programmers write code that humans can understand. Martin Fowler

    ×