Code metrics for your app
summary
Defines a module impact ratio that counts how many modules must recompile when one module changes, finds a 20% drop in monolith dependencies after modularization, and spots a single module that creates dependency cycles and forces recompiles. Uses Gradle Enterprise to show serial-execution spikes and a 6.9x parallelization metric. Dependency graphs are generated and processed with under 100 lines of Groovy, stored in SQLite via Exposed, and iterated weekly to guide targeted refactors.
AI-written summary · about
chapters (7)
- 0:00Introduction to code metrics
- 1:08Why define custom metrics
- 9:37Approach to defining metrics
- 13:32Modularization case study
- 36:24Implementation tips
- 38:10Other metric examples
- 39:40Q&A
related talks
35mHow we brought down our build times. Modularization impact on build speeds and metrics
36mImproving Gradle Builds
53mUsing Metrics to Take a Hard look at your code
21mStructuring modules in an Android app project
49mIdentifying bad design in codebases, objectively…
40mSimple Recipes to Enhance Developer Productivity
39mArch. App: Prioritizing Technical Debt as if Time and Money Matters
39mMobile Developer Productivity Panel