Find the 20 most frequently changing files in your project like so:

git log --name-only --pretty="format:" | sed '/^\s*$/'d | sort | uniq -c | sort -r | head -n 20

Next, run each file through a static analyzer and sort the files with the lowest code health as first.

These are your hotspots—the high-interest parts of the codebase where technical debt is most expensive unless paid back. Fix them next.

· · Web · 0 · 0 · 1
Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!