I've been building things for years. In private. On my laptop. In a Projects folder with 30+ started-and-stopped builds that nobody has ever seen. This week I stopped doing that.
I launched Builder's Path and made Long Game Athletics public. I posted about it on LinkedIn. And then something I didn't expect happened: people reached out. Not internet strangers leaving comments -- real conversations. People who connected with the story, who had their own projects sitting in their own folders, who wanted to talk about what it takes to go from "it works" to "someone will pay for it."
That was the lesson this week. Not a technical one. A personal one.
I've always been a creative person. Guitar, drawing, painting -- I've always needed something to make things with. Coding with AI tools became that outlet. The act of building is genuinely fulfilling. But I'd been treating it like a private hobby instead of something I share. And without sharing, you never find out if anyone cares. You never have the conversation that changes how you think about what you're building.
The part that surprised me most: being vulnerable worked. I didn't frame my 30+ unfinished projects as failures, because I don't think they are -- every one of them taught me something. But admitting publicly that none of them have paying users? That I'm still figuring this out? That landed with people. It turns out "I'm learning this in public and here's what I don't know yet" resonates more than "I'm an expert and here's my advice."
The conversations that came out of this week were worth more than any feature I could have built. Like-minded people who are on the same path, dealing with the same gap between building and launching. That's the thing I was missing when I was building alone.
What I shipped this week: Launched Builder's Path. Made Long Game Athletics public. Posted on LinkedIn. Had real conversations with real people.
What I learned: Building in private is safe. Building in public is useful.