Adrian WintersteinApr 10
Jocelynephiliac 

This all really good, love this. It's all analyzing social behaviors, not code at all.

"Five git commands that tell you where a codebase hurts before you open a single file. Churn hotspots, bus factor, bug clusters, and crisis patterns."

https://piechowski.io/post/git-commands-before-reading-code/

The Git Commands I Run Before Reading Any Code

Five git log commands that diagnose a new codebase before you open a single file: code churn hotspots, bus factor, bug clusters, and crisis patterns.

Apr 8 at 5:24pmWeb
Show threadDarius KazemiApr 8
@twipped holy cow this is good
Show threadjo.vaneyckApr 10

@twipped I'm getting strong behavioral code analysis/your code as a crime scene vibes, those are extermely valuable insights!

https://pragprog.com/titles/atcrime2/your-code-as-a-crime-scene-second-edition/

Your Code as a Crime Scene, Second Edition

Blends criminal psychology with code analysis to help you investigate and improve your code, software architecture, and organization.

Show threadTimothy WolodzkoApr 10

@twipped you could also add a bus factor calculation per file, e.g. like

for f in $(git ls-files); do
printf '%s\t%s\n' "$(git log --pretty=format:'%an' "$f" | { cat ; echo ; } | wc -l)" "$f"
done | sort -n

Show threadHRH ginsterbuschApr 10
@twipped which would be great, if only people would regularly and reliably use git .. but reality begs to differ *cries in klingon*
Show threadEgon Willigh☮gen 🟥Apr 27
@twipped awesome list! thanks!