VirtualTam's bookmarks
-
And more generally, "emacs as a <language> IDE":
- code completion
- snippet / templates
- project view
- syntax checking
- test harness utilities
See also:
-
2016-09-19 "Any way you look at it, a drum solo is a shitty gift for a newborn!"
-
2016-09-04 -
2016-01-05 -
2015-12-10 -
2015-08-05 -
2015-07-17 -
The French StackOverflow!
-
2015-04-08 -
2015-03-02 -
2015-01-16 -
2014-11-30 A follow-up to Mark Pilgrim's http://www.diveintopython.net/
-
Uses a project or repository's history to plot user contributions, displaying an elegant, colored graph of the file arborescence.
After running it on quite different projects...
- Python/Bash CI/Jenkins scripts
- Qt apps: GoldenDict, Psi+
- PHP website: Shaarli
...watching some vids on teh intartubez:
- Minecraft: https://www.youtube.com/watch?v=zRjTyRly5WA
- Linux kernel: https://www.youtube.com/watch?v=AhDiYPLo3p4
- Python: https://www.youtube.com/watch?v=cNBtDstOTmA
It allows to arbitrary spot some interesting implementation aspects (sorted by descending impact):
- language-dependent trees (oh hai Java packages ^^)
- framework-dependent trees
- project-management method (none, Agile, TDD)
Having a graphical tool also quickly shows:
- the overall structure of the project (a bit cooler than a simple $ tree, way quicker than loading the project on an IDE)
- the repartition of files (by extensions)
- who are the most active contributors
- what are the most modified files over time
- who does what: additions, deletions, refactoring
Some more CI-related matters:
- are there any tests?
- what is the source code / test code ratio? (we could expect a project/lib with N modules to have at least N test modules)
- who initiates / implements / optimizes test code?