Recomendados
Recomendados
Mais conteúdo relacionado
Semelhante a Visualizing project trends and code evolution
Semelhante a Visualizing project trends and code evolution (20)
Mais de Mark Needham
Mais de Mark Needham (13)
Último
Último (20)
Visualizing project trends and code evolution
- 1. Visualizing what’s happening on our project Mark Needham
- 2. Curious to see the trend with lines of code How big are our commits? Do people work in the same area of the code? Do the same people pair with each other? How many people work on an average story? Why?
- 3. “Budget for failure by designing and building toy systems that are similar to the systems you build at work in toolset but not in scope.” Breakable Toys
- 4. Demo of the graphs
- 5. Humble Shell Hacked together Scripts web app The evolution of the code
- 6. The humble shell script
- 7. JSON Jetty Web Server Text files
- 11. [ “Mark”, “Pat”] [“Alex”, “Charles”] Parsing git commits
- 13. Unit Testing!
- 16. { “Alex” : 1, “Charles” : 1, “Mark” : 2, “Added” : 1, “some” : 1, “important” : 1 } Parsing git commits
- 19. Uday/Liz: Did some stuff with mark logic ? Parsing git commits
- 20. Uday/Liz: Did some stuff with mark logic { “Mark” : 1, “Uday” : 1, “Liz” : 1, “did” : 1 } Parsing git commits
- 21. Uday/Liz: Did some stuff with mark logic { “Mark” : 1, “Uday” : 1, “Liz” : 1, “did” : 1 } Parsing git commits
- 22. Calculating lines of code
- 23. Abusing node
- 24. $ curl http://localhost:3000/git/update curl: (52) Empty reply from server Abusing node
- 26. git log -l30000 --no-merges --ignore-all-space --shortstat --ignore-all-space --pretty="format:%cd%n%s" --find-copies Parsing git extended history
- 27. git log -l30000 --no-merges --ignore-all-space --shortstat --ignore-all-space --pretty="format:%cd%n%s" --find-copies Parsing git extended history
- 28. Parsing git extended history
- 29. Parsing git extended history
- 30. Protovis RGraph Graphing libraries
- 31. Protovis RGraph Graphing libraries
- 32. High Charts
- 33. High Charts
- 34. Protovis
- 35. Protovis
- 36. The Pair Stair
- 37. Who started off working on a particular feature Whether people are avoiding working on XQuery What did we learn from these graphs?
- 39. Mark Needham @markhneedham The End
Notas do Editor
- We’re using a library called Step here to pass on the commits to the next function where it gets sent to the callback after being parsed
- Finally got to the point where it made sense to write unit tests around part of the code. Before that it was much quicker to just refresh and have a look what was going on
- Build a word cloud instead
- Build a word cloud instead
- Build a word cloud instead
- Build a word cloud instead
- Build a word cloud instead
- Build a word cloud instead
- Did it all on the fly to start with but Then realised it was way too slowSo pushed it into mongo
- If it’s actually synchronous – indicated by Nesting loads of functions then maybe It’s not a job for node
- If it’s actually synchronous – indicated by Nesting loads of functions then maybe It’s not a job for node
- If it’s actually synchronous – indicated by Nesting loads of functions then maybe It’s not a job for node
- If it’s actually synchronous – indicated by Nesting loads of functions then maybe It’s not a job for node
- If it’s actually synchronous – indicated by Nesting loads of functions then maybe It’s not a job for node
- If it’s actually synchronous – indicated by Nesting loads of functions then maybe It’s not a job for node
- If it’s actually synchronous – indicated by Nesting loads of functions then maybe It’s not a job for node
- High charts seems to be the best general purpose library but protovis is better if you want to make custom charts. Protovis is now d3.js
- You could go on holiday and then use these graphs to help you work out what had happened in your absence
- It was suggested that by making these graphs available that we’d encourage people to game the system to try and get to the top of the charts. In this case we weren’t sure if that’s necessarily bad because the Behaviour we wanted to encourage was people checking in in smaller increments than they had been previously.
- It was suggested that by making these graphs available that we’d encourage people to game the system to try and get to the top of the charts. In this case we weren’t sure if that’s necessarily bad because the Behaviour we wanted to encourage was people checking in in smaller increments than they had been previously.