The last day of my corporate job was a Thursday. I remember walking out of the office building, laptop bag slung over one shoulder, and thinking: that's it. No more standups. No more Jira tickets someone else wrote. No more pretending I cared about quarterly OKRs for a product I didn't believe in.
The first Monday morning alone was disorienting in a way I didn't expect. For six years, my calendar had been filled by other people. Now it was a blank white rectangle stretching into infinity. I sat at my desk at 8:30 AM and realized nobody was waiting for my status update. Nobody cared what I did that day. The silence was louder than any open-plan office.
I panicked, obviously. That first day I wrote exactly zero lines of code. I reorganized my Notion. I watched three YouTube videos about solo founder productivity. I had a minor existential crisis around 2 PM and went for a walk that lasted two hours. By evening, my only tangible output was a grocery list.
Tuesday was slightly better. I opened VS Code. I stared at the blank terminal. I typed mkdir xundao-ai and then sat there for another thirty minutes trying to decide what framework to use. (I went with Next.js. I always go with Next.js. The decision took far longer than it should have.)
Here's what nobody tells you about quitting your job to build alone: the hardest part isn't the code. It's learning to trust your own decisions again. In corporate, every choice has a committee attached to it. You can blame the architecture on the tech lead, the timeline on the PM, the bugs on the offshore team. When you're alone, every bad decision has exactly one person's name on it.
By Wednesday I had a working prototype - barely. It was a simple AI automation tool that took a user's natural language description and turned it into a workflow. The UI was ugly. The error handling was nonexistent. But when I typed "send me a Slack summary of yesterday's GitHub commits every morning at 9 AM" and watched it actually work, I felt something I hadn't felt in years. It wasn't pride exactly. It was more like relief. I could still do this.
The rest of the week was a blur of coding, breaking things, fixing them, and slowly remembering what it felt like to build something because I wanted to, not because a sprint board told me to. I deployed to Vercel on Friday afternoon. Zero users. Zero customers. Just a domain name and a bunch of code that existed because I decided it should.
Week 1 taught me something surprising: the blank calendar isn't the enemy. It's the point. The emptiness is where the work actually happens - not the cushy kind of work with peer reviews and deployment pipelines, but the raw, uncertain kind where you're standing at the edge of what you know and what you don't know, and nobody is going to tell you which way to jump.
I share more of the unfiltered reality at xundao.xin.
Top comments (0)