Vibecoding Is a Job Now

For twenty years the advice was learn to code. That era is ending, and the replacement is stranger. The machine writes the code now. The job is knowing what to build, saying it clearly, and catching the machine when it lies. People say vibecoding like it's a joke. I run a whole product this way, at night, alone. It's a job. I watch it become one in real time.

• A coding agent in a terminal. It writes most of the code on this site.
• A browser open next to it. I look at what it made, every time. Trust nothing you haven't seen run.
• My own voice. I describe what I want out loud, plainly, like I'd explain it to a contractor.
• A short leash. Small asks, shipped often. Big asks are where the lies hide.

1. Say the thing in plain words. Not specs. If I can't describe it at a kitchen table, I don't understand it yet.
2. Let it build. Then read what comes back. Not skim. Read.
3. Test it like a stranger. Click the buttons. Try to break it. The machine tests the happy path; the job is the unhappy one.
4. Ship small and often. A feature a night beats a launch a quarter.
5. Keep the judgment. Anything touching money, users, or promises gets my eyes twice.