Back to Overview

Vibecoding isn't about the code, it's about how much you care

1 day ago AI was used in this post Full disclosure: AI was used to format, write, and edit the content on this page.

Anyone can generate an app now. What separates okay software from great software is whether someone cared.

Vibecoding Isn't About the Code ​

Everyone can build software now.

Type a prompt, wait a few minutes, get an app. It runs. It mostly works. Ship it.

And that's exactly where most people stop.

Build, Ship, Move On ​

The typical vibecoded project looks like this: someone has an idea, generates it, posts a screenshot, and moves on to the next one.

Nobody ever tried the empty state, resized the window, or read the error message. And nobody used it for longer than the demo took to record.

I don't want to use products like this.

You can feel it within seconds. The buttons that almost line up. The loading spinner that never ends. The feature that exists because it was easy to generate, not because anyone needed it.

The code isn't the problem. Often the code is fine.

The problem is that nobody cared.

Care Is the Differentiator ​

When code was expensive, effort was a filter. If you spent six months building something, you probably cared at least a little.

That filter is gone. So care is now the only thing left that separates mid-to-okay software from great software.

Care is using your own product every day and fixing the thing that annoys you on day three. It's deleting a feature that doesn't earn its place, and asking the AI for a fifth iteration when the fourth was "good enough".

AI made the first 90% nearly free. The last 10% still costs what it always did: attention.

The model writes the code. You decide whether it's good.

Vibecoding doesn't lower the bar. It removes every excuse for not clearing it.