BUILDING IN KOREA
Manballers Devlog — Episode 04
Writing This in Public — Before I’d Even Bought a Domain
A question stopped me before I published a single word: if I write about this openly, does someone just take the idea? Here’s what changed my mind.
At some point it occurred to me: this whole process could actually be a blog. Not a developer with a polished changelog, but someone who doesn’t code, muddling through with an AI, hitting errors, getting things wrong, occasionally getting something right. That felt like it could be content.
And right behind that thought came the next one, immediately: if I post this publicly, doesn’t someone just take my idea?
01
The Question I Was Afraid to Ask
I asked Claude directly. “If I put this on a blog, isn’t someone going to steal my idea?”
The answer wasn’t what I wanted to hear, but it was clarifying. Ideas aren’t protected. Patents and trademarks protect execution — a specific product, a specific brand — not a concept sitting in someone’s head or in a blog post. Publishing a barefoot-walking map idea doesn’t stop anyone from legally building the exact same thing. That’s true of nearly every idea, not just mine.
02
Ideas Aren’t Protected. Execution Is.
Once I sat with that, it stopped feeling like a threat and started feeling like a fact I could work with. If the idea itself was never going to be defensible, hiding it wasn’t actually buying me anything.
Claude put it more directly than I expected: “There are far more startups that succeeded by going public and building a following than ones that succeeded by hiding the idea.”
There are far more startups that succeeded by going public and building a following than ones that succeeded by hiding the idea.
03
The Paradox of Going Public
Thinking it through further, the paradox made sense. Plenty of people will read a devlog and think “I should build something like that.” Almost none of them actually will. And even the ones who do start are already behind — someone else has a head start, a real audience, and a documented process.
If anything, the blog becomes proof I was here first. It becomes a brand story instead of a liability. And every post is a small chance to pull in the first real users before the product is even finished.
04
Writing in English, On Purpose
I already run a blog for an English-speaking audience, and my first instinct was worry — would a story rooted in Korea even land with readers outside it?
Looking into it, “non-developer builds an app with AI” turned out to be a genre with real appetite in English-language spaces. There’s an entire indie hacker culture built around exactly this: people documenting solo side projects as they go, and readers who actively want to follow along.
And barefoot walking wasn’t as Korea-specific as I assumed either — it already has an English name and an existing wellness audience: Earthing, or Grounding. The bridge to an international readership was already half-built before I wrote a word.
05
No Domain, No Trademark. Still Fine.
As of writing this post, I still haven’t bought manballers.com. I still haven’t filed a trademark, in Korean or English. Both of those decisions are on hold until after launch, once I know the direction is actually sticking.
There’s an order to this, and I’m trying to respect it. Domain and trademark come after conviction. Right now, the thing that comes first is building — and, it turns out, writing about the building.
So that’s the reasoning behind this blog existing at all. No hidden strategy, no perfectly timed launch plan — just a decision that being honest about the process, in public, was worth more than protecting an idea that was never really protectable in the first place.
Up Next
Episode 05 — Teaching a Database What a Good Spot Looks Like
Connecting Supabase, and the surprisingly human problem of deciding what actually counts as a “good” place to walk barefoot — soil quality, safety, shade, access — as a set of database columns.