i’m not saying don’t launch. launch. tell people. do the thing.
but if you’re sitting on something because you’re scared —
just push it live and go to bed.
the quiet ones find their people too.
there’s a type of developer that quietly builds something, tells nobody, and wakes up one day to find out people actually use it.
that feeling is unlike anything else in the world.
and it’s also the most terrifying thing that’s ever happened to me. here’s why 🧵
here’s what nobody tells you about building in public vs building in private:
when you announce, validation comes from the reaction.
when you don’t, validation comes from reality.
one of those hits completely differently.
nothing humbles you faster than watching a user interact with something you built.
they click things in an order you never imagined. they type things into fields you didn’t think were typeable. they find a bug in 30 seconds that your entire QA process missed.
claude code really said “let me just clean this up a bit” and deleted 200 lines of code i spent two weeks writing, replaced it with 12 lines that do the same thing, and had the AUDACITY to be right
i’m fine. this is fine. what even is coding
switching between a mac and a windows machine in the same day is a great way to spend 40 minutes doing the wrong keyboard shortcut and questioning every decision you’ve ever made.
my notes app has 47 startup ideas, 12 half-built projects, and one folder called “actually do this one” that i have opened exactly once.
i opened a new note tonight. it’s called “no seriously this one.”
unpopular opinion: vibe coding isn't lazy. describing what you want clearly enough for claude code to build it is a skill. a deeply unhinged skill, but still.
asked Claude Code to fix a bug. it fixed the bug, refactored three files, renamed a variable I've been spelling wrong for 2 weeks, and left me a comment saying "you might want to look at this later." I feel seen and judged simultaneously.