← Back to Writing

I didn't want to write code from my phone. I wanted to govern the whole chain.

From change to production — without opening anything else. Cursor on iPhone, GitHub, Vercel, staging review, then ship. The work we postpone often isn't the hard part. It's the part that costs too much to start.

View on LinkedIn

I didn't want to write code from my phone. I wanted to govern the entire chain — from change to production — without opening anything else.

The flow I built looks like this:

  • Cursor, from the app on my iPhone, is connected to my GitHub repository
  • GitHub is connected to Vercel, which handles builds and deploys
  • From the phone I write the prompt with the change I want
  • Cursor works and shows me the result in staging
  • I review before I touch production
  • If I like it, I ship to production

All from the phone. Without turning anything else on.

Speed isn't the point

What matters isn't how fast it runs. It's that I now orchestrate my projects from my phone. The barrier to starting is gone.

Minor changes now happen the moment they cross my mind — not when I find time to sit at a computer.

Review stays mine. The system proposes and prepares. I check staging. I decide whether it goes to production. I don't delegate the last word.

What this taught me beyond the setup

I learned something that applies past this workflow. The work we postpone often isn't the hard work. It's the work that costs too much to start.


Takeaway

Connect the tools end to end, keep humans on the staging gate, and remove the friction of “getting to a desk.” When starting costs almost nothing, small improvements stop piling up as someday tasks.