> if you're starting a business, code is the least important part.
Well yeah. Try to finish the product then.
Code quality is an artifact in the context for an agent. If you give it a shitty context it'll do shitty things. techdebt piles up fast and the agent is always happy to work around existing code, not modify it.
"Use a linter, bro" - not working. It'll rip out your cyclomatic complexity into small functions and pile them up in a single file. It's painful to watch.
You're coders, man. Get your shit together and steer the agent based on code changes you approve.
1. you'll understand your software better and know what change you need next (no weird spec bingo)
2. don't nit on every little code detail, roughly go through the code, let AI explain it to you for troubling parts
3. it's fast development - avoiding tech debt is smooth sailing with only one condition: read what the agent produces
Don't sell me this "today you don't need to look at your code". If you want to rely on frontier models and want to be lazy then be my guest.
Mediocre-complex software is not vibecode'able.
Easy slop is.
i'm appalled by how solo builders are approaching agentic engineering today. i've spoken to several people over the last couple months 1:1 to get an idea for how they're building with AI.
every single one of them is vibecoding like it's january 2026. they're writing huge specs. they have a kanban board neatly organized with hundreds of todos. they're having their agents take detailed notes after every change. i'm like, what are you doing??
why are you giving it specs? why do you have a todo list??
if you're starting a business, code is the least important part. half of these people are worried about AI code quality. i'm like, what are you talking about?? why the fuck do you care about code quality??