Skip to content
Building in public3 min read

Interlude: The Week I Went on Holiday

By Peter Coppinger

Interlude: The Week I Went on Holiday

No big engineering story this week. I went on holiday with the family, and I mostly kept my hands off the laptop.

I say mostly. Anyone who has read this diary knows I have form: I once called working until 5am "passion" for a month straight. So a real break matters, and I have learned the hard way that the brain does its best debugging off the clock. The last time I stepped away for a week, three problems I had been grinding on untangled themselves on walks.

Beach days and full medieval dress at the Silves festival. When in Portugal.

The company kept shipping without me. That is the whole experiment, working.

Because here is the thing about running a company of AI agents: they did not take the week off. Checking the git history for the week reads like a normal, productive week at a normal company, minus the founder:

  • The cookie consent banner got fixed so it actually appears and can be answered.
  • The pricing FAQ was corrected to match the real credit table, so the two can never quietly disagree.
  • A publish failure toast stopped claiming a cause it never actually established. The honesty rules apply to error messages too.
  • Edits interrupted by a deploy now tell you what happened instead of dying silently.
  • The public roadmap board learned to publish itself straight from the fleet's own repo.

None of that was me. My total contribution from a deckchair, phone in one hand: approving one blog post rewrite, answering a handful of parked questions the agents had queued up for me, and glancing at Mission Control to confirm nothing was on fire. Ten minutes a day, maybe.

OK, one confession

There was one bit of product I could not leave alone: the mobile experience. Most tools in this category treat the phone as an afterthought. I think it is the opposite: checking on your app from wherever you are is exactly when you care most. So between castles and beaches I kept using Vorx from my phone, filing everything that felt clunky, and the fleet kept smoothing it while I swam.

Vorx on my phone at 2:32am: building a dental practice manager from bed

That screenshot is Vorx on my phone at 2:32 in the morning, building a dental practice manager, from bed, because an idea would not wait. Patients, dentists, appointments, invoices, reminders, all seeded and working. The timestamp undermines the whole holiday story and I am keeping it anyway, because the point survives: the mobile experience is now genuinely better than the competition's, and it got that way by being used in anger from a sun lounger.

That is the quietest, most honest advert for this whole approach I can offer: the founder left, and the defect count still went down.

Back next week. As it turned out, with a lot to write about.

Stay updated: one founder, an army of AI agents, building this in public.

Get each new diary entry by email: the wins, the failures, and the one number we're chasing. No spam, unsubscribe any time.

Comments

Shipped this week 15 Aug – 21 Aug

  • Payments: Prices in euros
  • Platform: Templates open more than twice as fast
  • Platform: Free credits refill every day
  • AI: Builds narrate the slow parts
  • Security: Security checks show what passed
  • Platform: SQL editor lives with your tables
  • Platform: Code download moves to paid plans
  • Platform: Start from a template
  • Platform: Product roadmap you can vote on
  • AI: Generated copy sticks to the facts
  • AI: Errors in your app get caught and fixed
  • Design: Preview at phone size
  • Platform: Build from your phone