Analyze and Visualize Git Log for Fun and Profit - DevTernity 2015
•
2 gefällt mir•2,844 views
Presentation at DevTernity 2015 http://devternity.com/ Charts by eazyBI https://eazybi.com
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (19)
Ähnlich wie Analyze and Visualize Git Log for Fun and Profit - DevTernity 2015
Ähnlich wie Analyze and Visualize Git Log for Fun and Profit - DevTernity 2015 (20)
Mehr von Raimonds Simanovskis
Mehr von Raimonds Simanovskis (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Analyze and Visualize Git Log for Fun and Profit - DevTernity 2015
- 1. Analyze and Visualize Git Log For Fun and Profit Raimonds Simanovskis @rsim
- 5. Mining Rails — Learning from your App’s Lifeline Michael Feathers, Corey Haines RailsConf 2011
- 7. Ruby on Rails Git Log
- 8. Changes in Ruby files Birth of Rails Great Rails 3 refactoring RailsConf is coming
- 9. DHH contribution Rails is mine Let others contribute too Car racing takes all my time… OMG! I should give a technical talk at RailsConf! Don’t make this mistake anymore
- 10. Top contributors in 2015 by number of commits
- 11. Top contributors in 2015
- 12. 9-to-5 disciplined developer Hours of day warms up with small commits eats lunch at 12pm finishes work and socializes Aaron Patterson
- 13. Don’t judge someone by their appearance Hours of day @tenderlove
- 14. Don’t burn yourself! Hours of day José Valim Why don’t you sleep? Ruby on Rails contribution in 2012 Working on Elixir? Get angry and start deleting code?
- 15. Finding the best working pattern Hours of day Elixir contribution in 2015 José Valim
- 16. Contributions by time zone in 2015 US West coast Brasil Europe Japan India
- 17. Changes per day of week in 2015
- 18. Changes per hour on Fridays, in 2015 Beer time BDD
- 19. Linux > 0.5M commits > 20M lines of code > 70M lines of changes > 14K contributors
- 20. Changes over time Jan 1 1970 Apr 25 2037
- 21. Changes over time Jan 1 1970 Apr 25 2037 Apr 16 2005 Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
- 22. Top changed files
- 23. What is this large C++, C, Assembler project?
- 24. Changes over time Really? > 4M LOC?
- 25. Changes over time Really? > 4M LOC? #### Dependencies Node.js has several bundled dependencies in the *deps/* and the *tools/* directories that are not part of the project proper. Any changes to files in those directories or its subdirectories should be sent to their respective projects. Do not send your patch to us, we cannot accept it.
- 28. Top contributors
- 29. Ryan Dahl Creator of Node.js
- 30. Isaac Schlueter
- 31. Top contributors
- 32. John Resig Creator of jQuery
- 34. Huge Toad
- 35. Bonus WTF
- 36. Why duplicates?
- 39. There are only 2 hard things in CS Naming things Cache invalidation Off by one errors Time zones Unicode special characters