blob: 4feb9cd70fc87d2cae18022a5f14b96c2c1c318b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
# Analyze code quality through Emacs: a smart forensics approach and the story of a hack
Sunday, Nov 29 2020, 10:49 AM - 11:09 AM
Andrea
Emacs, show me how much technical debt and where it is in this
software repository!
Also how complex is this module?
And who is the main developer of this component?
Mmm, if I change this file, do I need to change something else, Emacs?
Ah, I need help of somebody to change this code! Emacs can you tell me
who knows something about this file?
The above are some questions my Emacs can answer (an M-x away).
It all started with "Your Code as a Crime Scene", an insightful book
by Adam Tornhill, and it continued with a big useful hack.
In this talk I want to show the analyses I can produce on software
repositories with my Emacs, explain how they help me in my daily work,
give a bit of context of how Adam came up with them, and show the
dirty code that makes this wonderful functionality work.
Back to the [[schedule]]
All times are approximate, and we might shuffle talks around as needed. Please check https://emacsconf.org/2020 a few days before the start of the conference for instructions on how to watch and participate.
<!-- automatically generated from submissions.org --->
[[!meta title="Analyze code quality through Emacs: a smart forensics approach and the story of a hack"]]
|
