Deep Dive

By the Numbers

The raw data behind 27 days of treating an AI as my primary development partner. Every tool call, every language, every commit — measured.

219

Total Sessions

170 analyzed in depth

5,172

Messages Sent

~191 per day

825

Commits Pushed

30.5 per day average

183,080

Lines Written

7,271 lines deleted

1,622

Files Touched

Across the full stack

1,026h

Compute Time

Claude thinking time

What Claude Actually Did

Claude Code has different tools for different actions. Here's how many times each one was called across all 170 sessions.

Bash

7,715Shell commands, git ops, builds

Read

3,660Reading files before editing

Edit

2,725Surgical text replacements

Agent

1,736Sub-agents for parallel work

Grep

1,198Code search across the codebase

Write

983Creating new files from scratch

Glob

612Finding files by pattern

The Bash dominance is real. 7,715 shell commands means Claude was running builds, git operations, tests, and system commands at a rate of ~285 per day. It ran more terminal commands in a month than most developers run in a year.

Languages Written

TypeScript

4,10575.4%

Markdown

74613.7%

JavaScript

4668.6%

HTML

931.7%

YAML

470.9%

CSS

450.8%

How Sessions Played Out

Multi-Task Sprints

Jumping between multiple workstreams in one session

Iterative Refinement

Repeated build-review-fix cycles on a single feature

Single Task

Focused execution on one well-defined goal

Exploration

Researching or understanding existing code

When I Work

Morning (6am–12pm)

76014.7%

Afternoon (12pm–6pm)

2,14841.5%

Evening (6pm–12am)

1,77134.2%

Night (12am–6am)

4939.5%

Eastern Time. Peak productivity: afternoon. Night owl sessions: real.

Multi-Clauding (Parallel Sessions)

I frequently ran multiple Claude Code sessions at the same time — one working on frontend, another on backend, a third on content. Here's how often the sessions overlapped.

161

Overlap Events

Times two sessions ran simultaneously

150

Sessions Involved

88% of sessions had overlaps

32%

Parallel Messages

Sent while another session was active

Derived Metrics

Messages per session

Average across 170 analyzed sessions

30.4

Commits per session

Each session shipped almost 5 commits

4.9

Lines per commit

Net lines added per commit on average

222

Files per session

Touching ~10 files per focused session

9.5

Sessions per day

Over 6 sessions every day for 27 days

6.3

Tool calls per message

Claude averaged almost 4 actions per response

3.7

The Bottom Line

30.5 commits per day. 6,780 lines of code per day. 191 messages per day. For 27 consecutive days. This isn't pair programming — it's having a development team that never sleeps, never takes a break, and types at the speed of an API call.

Get Glen’s Updates

Investing insights, new tools, and whatever I’m building this week. Free. No spam.

Unsubscribe anytime. I respect your inbox more than Congress respects property rights.

By the Numbers

What Claude Actually Did

Languages Written

How Sessions Played Out

When I Work

Multi-Clauding (Parallel Sessions)

Derived Metrics

The Bottom Line

Get Glen’s Updates

More From This Series

What Actually Worked

Everything That Broke

What's Next