When I joined the group, I couldn’t tell you what and APIwas

When Bas first added me to this group, I could barely have told you what an API was. I've been mostly quiet since, because I was heads down building something, and I finally get to show you.

But the win I want to share isn't the one I thought I'd be writing about.

A few weeks in, I was at my kitchen table testing a feature, and my own app wrote something back to me. A little message, the kind it sends to a stylist. I read it and I cried. Me. The person who built the thing. It had just made me feel seen, as a hairstylist, and I wasn't ready for that.

I'm a solo hairstylist. That's my actual job. The app is called Rooty, a companion for stylists who are tired of being told the only way to stay booked is to become a full time content creator. I built it between clients over about seven weeks.

Here's the part I think this group will appreciate, and it genuinely surprised me: the code was not the hard part.

The boring receipts:

212 commits, about seven weeks, built between appointments
One Python file, roughly 8,000 lines, zero dependencies, just the standard library
132 tests
Multi-tenant, real logins, running live right now with actual stylists signing up
Claude Code did the heavy lifting on the code, Anthropic's Haiku model runs the AI features
I directed all of it. Every product decision, every word of the voice, every call about what it should and shouldn't do. I'm not a programmer. I'm the person who knew what it needed to feel like.

That last line is the whole thing, so let me stay on it.

The code, honestly, the AI and I got through together. What I could not outsource, what no prompt handed me, was knowing when a message sounded like a brand instead of a friend. When it was technically fine and emotionally wrong. I felt those the way I feel a bad section in a haircut, right away, in my gut. And I sent them back.

So the "it feels like it gets me" that people react to, that came from real decisions:

The captions and replies learn from my actual writing, not a formula. They sound like a person because they're trained on one.
Every AI feature is its own little room with exactly one job. None of them is a general chatbot. A tool that tries to do everything feels like nothing. A tool that does one thing warmly feels like a friend.
And me. I was the reject button. I read hundreds of generated lines and killed every one that rang false.

One that stuck with me: early on, the app had a line promising nothing would "slip through the cracks." It sounded comforting. It also wasn't true, the app can only hold what you actually write down, and I knew the first person it let down would feel that broken promise. So I cut it. The AI wrote the comforting version. I had to be the one who knew that comfort you can't keep is just a betrayal with a delay on it. You only catch that if you've been the user.

Which brings me to the thing I actually learned, and I'm going to say it plainly even though it feels a little strange to.

I'm good at this. Not the code. The emotion and the impact. Knowing what "seen" feels like for a real person, and refusing to ship anything that missed it. For years I'd have called that the soft skill. Building this taught me it might be the whole skill. The machine can write the code now. It can't tell you when the code makes someone cry the good way. That part still needs a human who has lived it.

If anyone here is staring at an app that works but feels hollow, I think that's the gap, and it isn't a technical one.

Rooty's live at meetrooty.com if you want to look. Happy to get into how any of it is built. And thank you, genuinely, for being the room I get to finally say this in.

6 comments

When I joined the group, I couldn’t tell you what and APIwas