A modern programming language that makes developers happier.

kotlinlang

Hey guys, we are planning to modularize a pretty huge code base, right now 75% of the code lives in a legacy single module. I know the benefits of modularization but the ask for technical team is to come up with measurability metric i.e. how would we determine or what are the quantifiable metrics which we can provide to the leadership team/CTO. I installed `codeMR` and came up with things like code complexity, tight coupling, also cyclomatic complexity, so wondering if anymore pointers here which are measurable.

I think this is a good place to start, then explore the other modularization from recent droidcons referenced in this talk to see the development of a kind of module health theory. Interesting use of graph theory to define metrics that are indicative of 'good' modularization IMO. <https://www.droidcon.com/2022/11/15/modularization-flatten-your-graph-and-get-the-real-benefits/|https://www.droidcon.com/2022/11/15/modularization-flatten-your-graph-and-get-the-real-benefits/>