Œuvres de Adam Tornhill
Your Code as a Crime Scene: Use Forensic Techniques to Arrest Defects, Bottlenecks, and Bad Design in Your Programs… (2015) 55 exemplaires
Lisp for the Web 2 exemplaires
Patterns in C 1 exemplaire
Étiqueté
Partage des connaissances
Il n’existe pas encore de données Common Knowledge pour cet auteur. Vous pouvez aider.
Membres
Critiques
Statistiques
- Œuvres
- 5
- Membres
- 89
- Popularité
- #207,492
- Évaluation
- 3.4
- Critiques
- 2
- ISBN
- 6
That said, the techniques were useful. The book, at it's core, is about using data in the source code repository to get a broader understanding of a code base. The techniques are described in some detail, but the book leaned a bit heavily on a particular tool (Code Maat). I would have appreciated high level pseudocode versions of the various analysis techniques.
Throughout the book, we looked at several properties, all of which can be extracted from many source control repositories:
* change frequency
* lines of code -- the simplest proxy for complexity
* code churn (lines changed over time, rather than raw revisions)
* temporal coupling between code (files that are frequently changed together)
* authorship for expertise and churn (many authors)
* joint authorship to determine the social landscape of a project
The author also describes a number of interesting visualization methods and points to libraries that can generate them once you've extracted the raw data.
Note that Tornhill frequently warns that these are only heuristics. Although the framing around "forensic techniques" was rather thin, one important way that these tools are similar to tools of crime investigation is that they won't give you answers on their own. They will, however, point you at areas that warrant further investigation.… (plus d'informations)