I do not type much. I dictate almost everything I give an AI agent, using a tool called WhisperTyping that transcribes as I speak and keeps a copy of every recording. I had never really looked at that archive. Last week I went digging through it for something else entirely and realised I was sitting on a fairly unusual record: eleven months of one person talking to AI coding agents, nearly every day, timestamped.
So this is what came out of it. 14,625 recordings, 2,258,517 words, 332.7 hours of audio, from 26 August 2025 to 25 July 2026, across 292 active days out of 334. All of it me dictating prompts while building EF-Map and a few other EVE Frontier tools. Some of what I found matched what I would have guessed. A few things were the opposite of what I would have sworn was true.
How to read all of this
Every count is a literal string match over raw transcripts, so paraphrases are missed and transcription errors are included. Monthly charts run September 2025 to July 2026: August 2025 is a six-day stub, and July 2026 covers 1 to 25 July, which is why the volume chart is per active day rather than per month. The hour-of-day and ask-position charts use all 14,625 recordings. And in the spirit of the subject, I did not write the analysis code or the charts by hand. I dictated what I wanted at Claude and it wrote the Python and the SVG. Each chart has its underlying table underneath it if you want to check the numbers.
One more wrinkle. WhisperTyping caps a recording at 300 seconds, and when I hit the cap mid-thought I just start another recording and carry on, so a handful of recordings are really halves of one message. That happens ten times more often now than it did in September, 0.3% of recordings then against about 3% now, which is itself a sign of the messages getting longer. Stitching those continuations back together barely moves anything though: the medians shift by a word or two and the per-day decline gets slightly steeper, from 26% to 30%, so the charts count recordings the way the tool recorded them and the published figures are the conservative ones.
Fewer recordings a day, more words a day
The first thing I wanted was simply how much I was talking. Counting recordings alone is misleading if the recordings change length, so here is both, per active day, meaning a day I actually dictated something. That is not a working day in the Monday to Friday sense. As the last chart shows, plenty of them are Saturdays.
Table view
| Month | Active days | Recordings | Recordings per day | Words | Words per day |
|---|---|---|---|---|---|
| 2025-09 | 30 | 1,911 | 63.7 | 237,772 | 7,926 |
| 2025-10 | 27 | 1,235 | 45.7 | 149,239 | 5,527 |
| 2025-11 | 29 | 1,983 | 68.4 | 242,937 | 8,377 |
| 2025-12 | 30 | 1,072 | 35.7 | 134,232 | 4,474 |
| 2026-01 | 29 | 1,643 | 56.7 | 254,507 | 8,776 |
| 2026-02 | 22 | 1,200 | 54.5 | 186,818 | 8,492 |
| 2026-03 | 25 | 1,747 | 69.9 | 275,517 | 11,021 |
| 2026-04 | 28 | 907 | 32.4 | 163,380 | 5,835 |
| 2026-05 | 12 | 510 | 42.5 | 104,857 | 8,738 |
| 2026-06 | 30 | 1,119 | 37.3 | 245,137 | 8,171 |
| 2026-07 | 24 | 1,090 | 45.4 | 239,697 | 9,987 |
Comparing the first four months against the last four, recordings per active day are down 26% and words per active day are up 24%. On a day I dictate at all, I now speak less often and say more each time. The other thing hiding in that table is the number of days itself: September had 30 active days, July had 24. The month totals fell mostly because there were fewer active days, not because the days themselves got lighter.
The prompts nearly doubled in length
My median message went from 89 words in September to 164 in July. I would have told you the opposite happened. I assumed better agents meant less hand holding and shorter prompts, and the data says I used the improvement to say more per instruction instead.
Two things are tangled inside that rise, and they are worth separating. A recording counts as prompt-brokering if it mentions the word prompt, and a small number always did, which is why the blue line runs all the way back to September. Up to December those recordings carried only 5 to 11% of my words. In January I changed how I work: rather than mostly talking straight to one agent, I dictated into a second LLM and had it write the prompt for the coding agent. The strip under the chart shows that change directly: brokering jumped from 7% of my words in December to 42% in January, stayed near 45% until June, then fell back in July when I moved to an agent I mostly talk to directly again. Because brokering recordings are structurally longer, that shift alone lifts the overall median, which is why the chart splits the two modes.
Table view
| Month | Median words, direct | Median words, prompt-brokering | Brokering share of words |
|---|---|---|---|
| 2025-09 | 88 | 102.0 | 5.6% |
| 2025-10 | 76 | 119.5 | 6.4% |
| 2025-11 | 83.0 | 147 | 11.1% |
| 2025-12 | 86 | 154 | 6.8% |
| 2026-01 | 83.0 | 173 | 42.2% |
| 2026-02 | 82 | 171 | 42.9% |
| 2026-03 | 92 | 154.0 | 45.1% |
| 2026-04 | 109 | 184.5 | 47.9% |
| 2026-05 | 126.0 | 179.0 | 42.3% |
| 2026-06 | 133 | 219.0 | 47.4% |
| 2026-07 | 156.5 | 264.5 | 16.2% |
The interesting part is the amber line. Talking directly to an agent sat flat at 76 to 92 words for seven months, then started climbing in April: 109, 126, 133, 157. That is the genuine change, and it lines up with when agents got good enough to run unattended for long stretches. The better they got, the more I gave them per instruction. Both modes are still growing at the end of the data.
Eleven months, and my mouth does the same thing
One number refused to move. I have 332.7 hours of audio with exact durations, so I can work out how fast I actually speak. It is 113.1 words per minute across the whole corpus, and the monthly figure never leaves a band between 110.5 and 116.2, which is 5.2% wide.
Table view
| Month | Words per minute | Hours of audio |
|---|---|---|
| 2025-09 | 110.5 | 35.9 |
| 2025-10 | 115.7 | 21.5 |
| 2025-11 | 113.7 | 35.6 |
| 2025-12 | 113.6 | 19.7 |
| 2026-01 | 111.9 | 37.9 |
| 2026-02 | 114.3 | 27.2 |
| 2026-03 | 116.2 | 39.5 |
| 2026-04 | 111.1 | 24.5 |
| 2026-05 | 111.7 | 15.6 |
| 2026-06 | 112.0 | 36.5 |
| 2026-07 | 113.7 | 35.1 |
Four primary models, prompts nearly twice as long, a complete change in how the work is organised, and I am still talking at the same speed I was in September. Whatever prompt engineering is for me, it is not a change in delivery. It is just more words at the same pace.
The politeness collapse, and the word that survived it
This is my favourite thing in the data and the one I would never have predicted.
I used to say please to the machine, constantly. It runs at about 21 uses per 10,000 words for the first four months, falls off a cliff in January and February 2026, and settles around 8. Thank you went down harder still, from 3.9 per 10,000 words in September to 1.0 in July. I stopped being polite to it and I never noticed I had.
Sorry did not follow. 1,523 uses across the corpus, bouncing between 5.0 and 8.3 per 10,000 words with no real trend. By February please had fallen far enough that the two lines meet, and from there they travel together.
Table view
| Month | "please" count | per 10k words | "sorry" count | per 10k words |
|---|---|---|---|---|
| 2025-09 | 563 | 23.68 | 118 | 4.96 |
| 2025-10 | 315 | 21.11 | 80 | 5.36 |
| 2025-11 | 508 | 20.91 | 200 | 8.23 |
| 2025-12 | 273 | 20.34 | 70 | 5.21 |
| 2026-01 | 313 | 12.3 | 195 | 7.66 |
| 2026-02 | 101 | 5.41 | 114 | 6.1 |
| 2026-03 | 221 | 8.02 | 229 | 8.31 |
| 2026-04 | 129 | 7.9 | 90 | 5.51 |
| 2026-05 | 79 | 7.53 | 77 | 7.34 |
| 2026-06 | 251 | 10.24 | 178 | 7.26 |
| 2026-07 | 197 | 8.22 | 162 | 6.76 |
I think they were never the same behaviour even though they look like it. Please and thank you are deliberate courtesies aimed at something I half thought of as a person, and eleven months of familiarity wore them off the way it wears off with a new colleague. Sorry is not aimed at anything. It is a verbal tic, three quarters of it mid-sentence corrections like "the routing panel, sorry, the routing window", and you cannot wear that off because it was never a decision in the first place.
I bury the ask, and I did not know I did
When I dictate a long message the request almost never comes first. I set out where things are, walk through why, and only then say what I want. Across 3,823 messages the median request sits 83% of the way through, and 54% land in the final fifth.
Table view
| Position in message | Share of messages |
|---|---|
| 0 to 10% | 6.7% |
| 10 to 20% | 4.1% |
| 20 to 30% | 3.6% |
| 30 to 40% | 4.2% |
| 40 to 50% | 5.0% |
| 50 to 60% | 5.9% |
| 60 to 70% | 6.6% |
| 70 to 80% | 9.7% |
| 80 to 90% | 17.2% |
| 90 to 100% | 37.0% |
11% do lead with the ask, and those are not one-liners, because the sample only contains messages over 100 words. They are the ones where I gave the instruction first and justified it afterwards. The rest of the time the ask waits until the case for it has been made.
What I find interesting is that an LLM does the exact opposite. An assistant has only ever been trained to answer. Somebody asks, it replies, and leading with the answer is correct in that situation. But I am not answering, I am starting something, and when you start something the ask has to earn its place first. I suspect that mismatch is a big part of why AI-drafted posts read as pushy when nobody intended them to be.
The model carousel
Every recording is timestamped, so I can see which model I was on by which name I say out loud. Four primaries in eleven months.
Table view
| Month | Copilot | Opus | GPT | Codex | Fable |
|---|---|---|---|---|---|
| 2025-09 | 3.79 | 0.0 | 1.93 | 0.8 | 0.0 |
| 2025-10 | 2.55 | 1.07 | 1.74 | 0.34 | 0.0 |
| 2025-11 | 2.72 | 0.12 | 0.33 | 0.08 | 0.0 |
| 2025-12 | 1.64 | 0.6 | 0.22 | 0.0 | 0.0 |
| 2026-01 | 2.0 | 0.9 | 1.22 | 0.24 | 0.0 |
| 2026-02 | 3.59 | 11.67 | 2.19 | 0.64 | 0.0 |
| 2026-03 | 0.98 | 13.97 | 1.34 | 0.04 | 0.0 |
| 2026-04 | 3.43 | 6.61 | 9.79 | 4.35 | 0.0 |
| 2026-05 | 2.77 | 0.0 | 4.01 | 3.53 | 0.0 |
| 2026-06 | 1.02 | 5.75 | 3.71 | 1.79 | 2.33 |
| 2026-07 | 0.08 | 3.25 | 1.08 | 0.04 | 6.68 |
Copilot holds steady at two to three mentions per 10,000 words right through to May, then falls off a cliff: two mentions in the whole of July. Opus arrives in February and owns February and March, peaking at 14.0. April and May are a GPT and Codex detour, with GPT at 9.8 in April and Opus at exactly zero mentions in May. Then Fable appears on 11 June and is at 6.7 within six weeks. I did not consciously decide any of those switches. I just followed whatever was doing the job at the time.
The other thing in there is what is not in there. Grok gets one mention in 2.26 million words, Kimi none. For all the tool shopping, I never really left the big labs.
There is no weekend
Table view
| Hour | Share | Hour | Share |
|---|---|---|---|
| 00:00 | 3.06% | 12:00 | 6.68% |
| 01:00 | 1.87% | 13:00 | 6.67% |
| 02:00 | 1.43% | 14:00 | 6.55% |
| 03:00 | 1.23% | 15:00 | 6.11% |
| 04:00 | 1.03% | 16:00 | 5.78% |
| 05:00 | 0.96% | 17:00 | 5.94% |
| 06:00 | 1.63% | 18:00 | 5.43% |
| 07:00 | 2.08% | 19:00 | 5.61% |
| 08:00 | 2.54% | 20:00 | 5.11% |
| 09:00 | 5.22% | 21:00 | 4.96% |
| 10:00 | 5.57% | 22:00 | 4.75% |
| 11:00 | 6.19% | 23:00 | 3.62% |
679 recordings land between 2am and 6am. Normalised per calendar day, Tuesday is my busiest day and Friday my quietest, and Saturday and Sunday sit in the middle of the pack rather than at the bottom. The weekend does not exist as a category. I was active on 292 of 334 days, with only four breaks longer than three days in the whole period, the longest being ten days in May.
The dataset also passes the sanity check I wanted from it. The word hackathon appears zero times in 2.26 million words until 12 February 2026, the day the EVE Frontier hackathon was announced, then jumps to 19.6 per 10,000 words that month. The event itself ran 11 to 31 March, so everything before that was planning: a staging repo, a local devnet, a lot of markdown documents. My three busiest days in the entire corpus, 3 March (193 recordings), 2 March (175) and 18 February (153), all land in that planning window rather than in the hackathon itself, which I think is because a planning document comes back in minutes where code takes an agent a long stretch, so the dictation loop spins much faster. If a spike that obvious had not landed where I knew it should, I would not trust anything else on this page.
Why any of this matters
I did not set out to measure myself. I was trying to build a writing style profile so that when I ask an LLM for a Discord post it does not come back sounding like a press release. The measurements were a side effect, and they turned out to be more useful than the thing I was after.
The bit I keep coming back to is that eleven months of daily use changed almost everything about how I work and almost nothing about me. The tools turned over four times. The prompts nearly doubled. The manners quietly evaporated. And underneath it all I am still talking at 113.1 words a minute, still explaining myself before I ask for anything, still calling myself a vibe coder in the same breath I used in week two.
If you dictate to agents and you have an archive sitting there, it is worth a look. I would be interested to know whether the politeness thing happens to everyone or whether that one is just me.