Re: Code health metrics

How large is your Clojure codebase? On Wednesday, July 2, 2014 6:33:42 AM UTC-7, Chris Ford wrote: > > A little more context on what I'm considering. > > I work in a team of about 10 developers on a Clojure project. In the > larger enterprise there are mainly Java applications. > > I'm intereste

Re: Code health metrics

A little more context on what I'm considering. I work in a team of about 10 developers on a Clojure project. In the larger enterprise there are mainly Java applications. I'm interested in a way to visualise which parts of the codebase are getting sticky and might require intervention. As well as

Re: Code health metrics

Hi Chris, I have long collected metrics on various Clojure code bases, and have had grand plans for automating the process with an open source tool. The metrics you look at depend heavily on what you care about - the most telling metrics I've used recently are Assertion Density [1], an adaption

Re: Code health metrics

Hi Chris, Dynalint can help identify undefined behaviour. Thanks, Ambrose On Wed, Jul 2, 2014 at 4:53 AM, Chris Ford wrote: > Hi all, > > Are there any good tools for measuring the health of a Clojure codebase? > What is even useful to measure for Cloju

Re: Code health metrics

My toolbox is: lein-cloverage (mostly vanity), Midje (TDD), Eastwood (to decrease wtf/minute) + lein check (once in a while). No fancy cyclomatic coupling hyperdrives. Metrics become more important in larger teams, say 3+ people. They don't add much value for small teams as everyone can follow up

Code health metrics

Hi all, Are there any good tools for measuring the health of a Clojure codebase? What is even useful to measure for Clojure? Afferent/efferent coupling, cyclomatic complexity and unit test coverage are metrics I would use for Java, but do they apply equally to Clojure? I'm aware of Clique