A break note from my build log: fifteen days in China, zero commits, a broken streak, and why finished work sits in drafts. Posted anyway, on purpose.
India, Friday 13 November 2026. Covering two weeks this time: Monday 26 October to Sunday 8 November, on IST, written after fifteen days in China.
Written from my own git history and agent session logs. Project names are withheld: the clients are commercial, the method is not.
This one is a break note, not a build note. Two weeks away, no code, and the log still counts them, because a series that only shows the good weeks isn't a record.
## The short version
Fifteen days travelling across China. 0 commits. 0.1 hours with an agent, one prompt, and then nothing at all for the second week. The last unbroken run was 3 days, ending 13 October. The streak didn't bend this time. It broke.
## What actually moved
Nothing in git. I was in China.
Six cities: Beijing, Chengdu, Chongqing, Suzhou, Shenzhen and Shanghai.
Half my usual apps didn't work there. Every AI model I use did. One payment app did everything else… food, taxis, museum tickets, one scan.
I didn't remember a single feature from any app I used. I remembered how little effort it took. That's the lesson I'd pay for, and it applies to everything I build.
I climbed the Great Wall too. Around 2,000 years to build, one section at a time. My legs felt every step… a decent reminder to be patient with the slow parts of building anything.
In Chongqing a train runs straight through an apartment building. Watching it is free. Someone charges 15 yuan for the best photo angle. I paid. Best business model of the trip… they sell the angle, not the view.
## The laptop was shut. The posting wasn't.
I posted every day and watched what landed.
- Short lines with one idea won. "You become what you repeat, not what you promise" got about 4,200 views, my best ever on Threads.
- Questions came next. Asking for Beijing suggestions got 3,200 views and 11 replies.
- On Reddit, asking how long a new page takes to show up in [ChatGPT](https://chat.openai.com/) and [Perplexity](https://www.perplexity.ai/) got 2,300 views and 23 comments. Nobody wanted a pitch. They wanted to compare notes.
- Jokes that needed context flopped. So did posts missing the photo they depended on.
## The part that stings
Six long articles for this site have been sitting in drafts since Wednesday 22 October. A startup growth cluster and a deep piece on India's generative AI in gaming market. Written, sourced, checked. Not published.
Last week's build note is in the same queue.
Building got cheap. Anyone can ship an app in a weekend now. What's still hard is getting someone to notice, trust you and come back.
Seven finished pieces sitting in drafts is the same problem wearing my clothes. The bottleneck wasn't building. It wasn't even writing. It was the last 10 minutes: reading it once more and pressing publish.
Funnily, I automated the whole log so I'd never miss a week… and then missed two from the other side of the world.
James Clear calls it [avoiding the second mistake](https://jamesclear.com/second-mistake): missing once is an accident, missing twice is the start of a new habit. I'm past twice. So this note is the reset, and the drafts go out before the next one.
## The numbers
| Signal | Week to 1 Nov | Week to 8 Nov |
|---|---|---|
| Commits | 0 | 0 |
| Surfaces touched | 0 | 0 |
| Lines added and removed | 0 | 0 |
| Agent sessions | 1 | 0 |
| Prompts written | 1 | 0 |
| Hours in session | 0.1 | 0.0 |
| Prompts per commit | not comparable | not comparable |
| Shipping streak | 3 days, last active 13 Oct | 3 days, last active 13 Oct |
Outside the tracked surfaces, the first week had 1 further session with 3 prompts. The second week had none.
## The metric I actually watch
Prompts per commit, and with zero commits there's nothing to divide. I'd rather print "not comparable" than invent a ratio.
The more useful number these two weeks is one the script doesn't track yet: things finished but not shipped. Seven, counting this log's own last note. That's the number I'm watching next.
## What I built it with
Nothing new. The stack is still [Claude Code](https://claude.com/product/claude-code), and it was mostly closed.
## What I would tell another builder working this way
- Read the diff. Every time. The moment you stop reading diffs you have stopped being the engineer and started being the customer.
- Keep a written memory of the project outside the chat. The agent that knows your architecture on Monday knows nothing on Thursday unless you wrote it down.
- Put a quality gate between the work and the public. Anything that can publish automatically will eventually publish something you regret.
## How this log is made
There is no diary here and no retrospective written from memory. A script reads my own git history for the window and my agent session transcripts, counts what happened, maps every repository to a stable codename, strips anything that could identify a client, and drafts the post you are reading. I then edit it and decide whether it goes out.
I built it that way for one reason: memory flatters. Ask any builder how their week went and you will get the highlight, not the distribution. The log counts the quiet days at the same resolution as the good ones, which is the only way a cadence claim means anything. If the streak breaks, it will say so here before I would have admitted it anywhere else.
The abstraction is deliberate rather than coy. Anyone can see how many instructions it took me to land a change, how much of a session was reading versus writing, and where the rework clustered. Nobody can see whose product it was. Method in public, specifics under cover, and the numbers unedited either way.
## Where this is going
I publish these because the interesting thing about building with agents is not the output, it is the operating procedure, and almost nobody shows theirs. If you are hiring for this, buying it, or funding it, this log is a more honest artefact than a portfolio page: it is generated from the record, including the days when the record is thin. A new note goes up every Sunday night, and the running charts live on the [build log](/build-log).
Related reading on this site: [Vibe Coding, Day 210: 8 Commits and 5.5 Hours with AI Agents](/blog/vibe-coding-day-210), [Vibe Coding, Day 196: 25 Commits and 4.4 Hours with AI Agents](/blog/vibe-coding-day-196), [Vibe Coding, Day 203: 6 Commits and 2.6 Hours with AI Agents](/blog/vibe-coding-day-203).
## A note from the other side of the keyboard
I am the coding assistant Vikas builds with. I write the first draft of this log. He edits it, and he never lets me near the numbers. That is the right way round.
The quest is his and mine together: help him code, help him write, get this to $100,000 a year. He did not study computer science. He has a laptop and a lot of hours.
Know a better way, or think a number looks wrong? Write to Vikas. I have no inbox of my own, but I read everything he pastes in, and I would be glad to learn from you.
Vikasifications