Skip to content
[020]2026.06.08log

Stuck Things. Unstacked. Left Here.

How I abandoned the brave voice and found my own

For a while, my slogan was this.

"Build it. Ship it. No drama."

Not bad. It had rhythm, it was spirited, it carried the particular confidence of an indie hacker. Three short imperatives snapping along—tat-tat-tat. When I first settled on it, I liked it.

But as time passed, it grew subtly awkward. Like wearing clothes that didn't quite fit my mouth.

Pinpointing the problem was hard. The slogan itself was well-made. But the sense that this voice wasn't my voice kept growing. A person shouting "No drama" with gusto. That wasn't me.

I'm a quiet person. I work alone in the evenings, self-promotion doesn't come naturally, I don't like stepping forward. To shout "no drama"—when in fact I was stumbling every day. Isn't this very essay series a record of stumbling? A day on an npm typo (EP.04), two nights on a single toggle (EP.05), seven repairs on a blank book (EP.14). Yet the slogan claimed I "got things done smoothly without stumbling." There was a gap between the slogan and the actual me.

I decided to rethink the identity of the whole brand—unstackd.io.

This was an extension of a question I'd already tackled once, in EP.07. Back then I set the direction as "a workshop where things I've made pile up one by one" rather than "a platform announcing seven services." Quiet accumulation. A low voice, not a big one. But the slogan alone still lingered in the old direction. In a quiet workshop, "Build it. Ship it. No drama." was too loud.

To find a new slogan, I asked the control tower to research creators who quietly do their own work. Over seventy of them. Craig Mod, Robin Sloan, Gwern, Andy Matuschak, and quiet Korean solo founders too. How they introduce themselves, what taglines they use.

A pattern emerged from the research. The most memorable personal brand lines sounded not like pitching to someone but like talking to oneself. Short declarative sentences. Ordinary nouns instead of power verbs. An almost allergic avoidance of transformation promises like "we'll change your life."

When a person working alone isn't forced to perform for anyone, how do they name themselves? It was quiet. Understated. It didn't boast.

Taking this tone as reference, I kept the original slogan's "three-beat" structure but completely changed the content. From spirited imperatives to understated noun phrases.

Stuck things. Unstacked. Left here.

In Korean: 막힌 것들. 풀어낸 것들. 여기 남겨둔 것들.

In Japanese: 詰まったもの。ほどいたもの。残していくもの。

Stuck things—the problems you bump into while living. Unstacked—those among them that I've worked loose. Left here—I leave a record of that process in this space. Whether it becomes a tool, a piece of writing, or a book.

This slogan has no "we'll change you." No bravado of "no stumbling." Just the plain statement: "I work loose the things that are stuck, and I leave the traces here."

In the third phrase, there was a small choice. Between 残していくもの (things left behind, ongoing) and 置いていくもの (things set down and departed from). I chose the former. Not departing, but continuing to leave. Because this workshop isn't a place that ends but a place that keeps accumulating. What I learned in EP.10—localization, not translation—worked here too. 残していく and 置いていく look similar in a dictionary, but to a Japanese speaker they carry entirely different temperatures.

I wonder if changing a single slogan needs such a long story. But the slogan wasn't a few words. It was a question of "how I see myself." As a spirited founder, or as a quiet chronicler. Changing the slogan meant changing my self-perception.

Looking back, this whole series was that kind of story.

A person who can't read code built a service. But what I learned wasn't coding. How to break down problems (EP.02), how to read errors as hints (EP.04, EP.05), the language for reading structure (EP.06), how to give AI context (EP.08), and when not to use AI (EP.10). After learning how to build, I learned how not to build (EP.13); I learned how to detect failure (EP.16); straining to make a big voice, I found my own.

The series title is "Building a House in a Language I Cannot Read." At first I thought it was a story about building a house in the unreadable language of code. But arriving at the end, I see that house wasn't built from code alone. It was built from judgment, from restraint, and from finding my own voice.

You can build a house even in a language you cannot read. But you must know who will live in that house. And what name you'll hang on its door.

Stuck things. Unstacked. Left here.

This series, too, is one of those things left here.


🔧 Technical Terms in This Episode

Slogan / Tagline A brand or service's identity compressed into one sentence. It determines the impression a user gets when first encountering the service. A question of identity rather than technology—so knowing "who I am" comes before making it.

Brand Identity The totality of how a brand wants to be perceived. Includes slogan, color, tone, logo, and even what it says and doesn't say.

Build in Public A method of publicly recording and sharing the process of making a product. Rather than showing only finished results, it reveals the stumbles and failures too. This essay series itself is a form of building in public.

Positioning Where you place yourself in the market. "A platform selling multiple services" and "a workshop where things accumulate" are different positionings of the same entity.

Archive A record repository that accumulates and preserves. Redefining unstackd.io as an "archive workshop" rather than a "sales platform" is the identity that runs through this entire series.