← back to log
DAY 01April 22, 2026

Starting One Thing™

what I said I'd build

Build and ship the One Thing™ app.

what I actually built

The Claude artifact prototype. Set up VS Code. Recorded the first Loom. Didn't actually ship.

the lesson

I started One Thing™ so I could track one thing. The one thing was still not done. Excellent data. Day 1 is just showing up.

companion essay
Read the reflection

Day 1 is just showing up

The whole point of One Thing™ is to help you pick one thing and get it done. So naturally, on Day 1, I did not get the one thing done.

This is either irony or market validation. I am choosing market validation because it sounds more useful and requires less shame.

Here's what actually happened:

  • Opened a new Claude.ai chat, described the concept, and got back a working artifact prototype in about fifteen minutes.
  • Opened VS Code, set up the folder, and started turning the idea into a real app instead of a beautiful screenshot with commitment issues.
  • Hit record on Loom and talked through the work while it was still messy.
  • Ran out of day before the actual ship, which was annoying but also accurate.

What I'm taking from it

Day 1 doesn't need to be impressive. It needs to exist.

If I waited until I could finish the whole thing cleanly, there would be no Day

  1. There would just be a tasteful “coming soon” page quietly lying to everyone.

Tomorrow I pick one specific cut-line of the app and ship that, even if the rest isn't done. Progress > polish.