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