> Commit count by month, for the entire history of the repo. I scan the output looking for shapes. A steady rhythm is healthy. But what does it look like when the count drops by half in a single month?

Let's NOT jump to conclusions; it could mean many things. For example, a period with other priorities, different urgencies, other issues external to the project itself and beyond our control, vacations, illnesses, or anything else that could impact the commit history.

I think these considerations and the others expressed in this article can easily lead to hasty conclusions and erroneous deductions, too simplistic.

Coding flow, like business needs, cannot always be objectively and deterministically measured.