The App Was Never the Hard Part

Everybody's a builder now. You open Claude Code or Cursor, noodle on a prompt for twenty minutes, and by Sunday night you've got a working app with auth, a database, and a Stripe checkout that actually processes a payment. I've done it. You've probably done it too. The first time it happens you feel like a wizard.

And then the silence hits. You post it, you tell a few friends, maybe you drop it in a Discord... and nothing. Not "this sucks" nothing. Just nothing. No signups, no comments, no [censored] given, LOL.

That silence is the lesson. And it's the same lesson that's existed since the first person built the first piece of software, it's just louder now because building got so cheap that everyone's tripping over it at the same time.

Here's the thing nobody wants to hear: writing the code was always the easy part. Even before AI, a decent dev could smack out an MVP in a few weeks if they knew what they were doing. What separated the businesses that made money from the ones that didn't was never "can this thing technically function." It was always two other questions. Does anyone actually want this. And will anyone find out it exists.

AI didn't change that equation. It just deleted the excuse. Ten years ago you could tell yourself "well, building takes so long, once I ship, people will obviously flock to it." Now you ship in a weekend and get to watch, in real time, that shipping was never the bottleneck. The market doesn't care how fast you built it. It cares whether it needed to exist.

I think of it like the crepe analogy I keep going back to. Your first crepe is trash. Everyone's first crepe is trash. But with vibe coding, people are getting a hundred crepes an hour now instead of one a day, and they're shocked that crepe number ninety-four is still trash if the batter (the actual idea, the actual customer, the actual problem) was never right to begin with. You can iterate on execution speed all day. Speed doesn't fix a batter problem.

So what's actually hard, if it's not the build?

1) Finding a problem someone will pay to make go away. Not a problem you find interesting. Not a problem that's fun to build for. A problem with a wallet attached to it. This is why everyone harps on solving a problem YOU have first when first starting out with ICM folders.

2) Getting in front of the people who have that problem, over and over, until some of them notice you exist. This is marketing, and it's a PITA, and there's no prompt that does it for you. Nobody's shipped an agent that goes and builds you an audience while you sleep. If they had, we'd all be using it and none of us would need day jobs.

3) Doing the unglamorous rinse and repeat of talking to users, getting told your baby's ugly, and changing the thing anyway. This is the part vibe coders skip because it doesn't feel like building. It feels like admitting you might be wrong. Most people would rather generate app number six than sit with the fact that app number one to five never had a real customer behind them.

At the end of the day, AI gave us a superpower and a blind spot in the same box. The superpower is real, I'm not gonna pretend it isn't, I can build in an afternoon what used to take me a month, and that's genuinely useful. But the blind spot is that building fast makes it feel like progress even when you're just generating more trash crepes faster. Motion isn't traction. A deployed app with zero users isn't a business, it's a hobby with a URL.

None of this is new. Go read Rory Sutherland's Alchemy and you'll see the same idea from a non software angle, that the "obviously logical" solution rarely wins, the one that understands people wins. Software has just made that truth impossible to hide behind anymore. You can't blame the tooling. The tooling's fine now. It's almost too good.

How many of you made something and just heard crickets when you showed it off?

6 comments

The App Was Never the Hard Part