Coding Days
Activity Volume
days
Counts the number of distinct days with at least one commit.
💡 Like tracking how many days a chef actually cooked versus planned, sourced, or managed, coding days show actual hands-on development time.
What It Measures
Counts the number of distinct days with at least one commit.
Why It Matters
Tracking consistency of coding activity
Understanding how many days you actively write code
How It's Calculated
Counts each unique day that has at least one commit in the date range.
COUNT(DISTINCT DATE(commit.timestamp) WHERE timestamp BETWEEN measure_from AND measure_to)Concrete Example
If a developer commits on 12 of 22 working days, their coding day ratio is 55%, they are actively writing code slightly more than half the time.
What Does a Healthy Score Look Like?
Balance matters, too few days suggests little output, too many can mask shallow work.
Healthy
8–15 coding days in a 22-day period (60–70%)
Watch Out
Under 5 days (very low activity) or all 22 days (possible burnout risk)
Needs Attention
Consistent decline over multiple periods without explanation
What Moves This Metric?
Goes up when…
Active feature development with daily commit habits
Smaller, frequent commits rather than large end-of-day dumps
Fewer meetings and administrative tasks protecting coding time
Goes down when…
More time spent in planning, reviews, and meetings
Blocked on dependencies leaving little active coding to do
Vacation, illness, or on-call duties reducing hands-on time
Start Tracking Coding Days
Connect GitHub and Shortcut in minutes. All metrics update automatically.
Engineering metrics and developer well-being platform. Track 50+ metrics, AI-powered insights, and Dynamic Archetypes for just $10/active user/month.
contact@projcity.com