Building by describing intent instead of typing most of the code — how far does that go?

Options

• For some founders it is already the main loop: intent, review, iterate — code is an artifact.
• It is a phase for hype cycles, not the whole job; hard systems still need hands-on engineering.
• Manual coding stays essential wherever performance, safety, or subtle state matters.
• Future engineering looks like managing agents in chat with budgets, tests, and rollback plans.
• You still need taste to reject plausible wrong solutions — the hard part moved upstream.
• Teams that stop reading diffs will ship fast and firefight forever.
• It helps non-engineers participate, which changes product but also blurs ownership.
• I enjoy it for greenfield; maintaining legacy through vibes sounds miserable.
• Regulated domains will lag years behind Twitter takes about vibe coding.