How I Audit a Legacy Rails Codebase in the First Week

Though not an overly experienced programmer, I see that e.g. in my previous job, also a legacy rails app, this kind of attention on test coverability to important models/controllers would have been helpful.

I appreciate these kinds of breakdowns because they highlight how understanding complexity isn't really about the metrics so much as how you can use them (like LOC or test coverage but where they're clustered) to identify the pain points. Some of these heuristics were new to me too so this is super helpful.

Particularly, I really like how they mention auditing the schema. The data model is the fundamental backbone of the application so it makes sense that you'll find foundational problems in there. I don't think it's possible for an application to have fucked up DB tables and a perfectly reasonable application layer.