VirtualTam's bookmarks

  1. Ode to Spot 2016-11-16

    Felix Catus is your taxonomic nomenclature, An endothermic quadroped, carnivorous by nature. Your visual, olfactory, and auditory senses Contribute to your hunting skills and natural defenses. I find myself intrigued by your sub-vocal oscillations, A singular development of cat communications That obviates your basic hedonistic predelection For a rhythmic stroking of your fur to demonstrate affection. A tail is quite essential for your acrobatic talents: You would not be so agile if you lacked its counterbalance; And when not being utilitized to aid in locomotion, It often serves to illustrate the state of your emotion. Oh Spot, the complex levels of behavior you display Connote a fairly well-developed cognitive array. And though you are not sentient, Spot, and do not comprehend, I nonetheless consider you a true and valued friend. -- Lt. Cmdr. Data, "An Ode to Spot"

  2. 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:

    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?