[[!meta title="Analyze code quality through Emacs: a smart forensics approach and the story of a hack"]]
[[!meta copyright="Copyright © 2020 Andrea"]]

Back to the [[schedule]]  
Previous: <a href="/2020/schedule/23">Incremental Parsing with emacs-tree-sitter</a>  
Next: <a href="/2020/schedule/25">Traverse complex JSON structures with live feedback</a>  


# 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 EST /  7:49 AM -  8:09 AM PST /  3:49 PM -  4:09 PM UTC /  4:49 PM -  5:09 PM CET / 11:49 PM - 12:09 AM +08  
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]]  
Previous: <a href="/2020/schedule/23">Incremental Parsing with emacs-tree-sitter</a>  
Next: <a href="/2020/schedule/25">Traverse complex JSON structures with live feedback</a>  


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. See you then!
<!-- automatically generated from submissions.org using conf/generate-schedule-files --->