What is Vibe Coding?
Notes from a talk by S Anand:
What is vibe coding?
It's where we ask the model to write & run code, don't read the code, just inspect the behaviour.
It's a coder's tactic, not a methodology. Use it when speed trumps certainty.
Why it's catching on
- Non-coders can now ship apps - no mental overhead of syntax.
- Coders think at a higher level - stay in problem space.
- Model capability keeps widening - the "vibe-able" slice grows daily.
How to work with it day-to-day
- Fail fast, hop models - if Claude errors, paste into Gemini or OpenAI.
- Cross-validate outputs - ask a second LLM to critique or replicate; cheaper than reading 400 lines of code.
- Switch modes deliberately - Vibe coding when you don't care about internals and time is scarce, AI-assisted coding when you must own the code (read + tweak), Manual only for the gnarly 5 % the model still can't handle.
What should we watch out for
- Security risk - running unseen code can nuke your files.
- Quality cliffs - small edge-cases break; drop the use case or wait for next model upgrade.
What are the business implications
- Vendors still matter - they absorb legal risk, project-manage, and can be bashed on price now that AI halves their grunt work.
- Prototype-to-prod blur - the vibe-coded PoC could be hardened instead of rewritten.
- UI convergence - chat + artifacts/canvas is becoming the default "front-end"; underlying apps become API + data.
How does this impact education
- Curriculum can refresh term-by-term - LLMs draft notes, slides, even whole modules.
- Assessment shifts back to subjective - LLM-graded essays/projects at scale.
- Teach "learning how to learn" - Pomodoro focus, spaced recall, chunking concepts, as in Learn Like a Pro by Barbara Oakley.
- Best tactic for staying current - experiment > read; anything written is weeks out-of-date - Experimenting is far superior to reading these days
What are the risks
- Overconfidence risk - silent failures look like success until they hit prod.
- Skill atrophy - teams might lose the muscle to debug when vibe coding stalls.
- Legal & compliance gaps - unclear license chains for AI-generated artefacts.
- Waiting game trap - "just wait for the next model" can become a habit that freezes delivery.
Also see - "How I use LLMs" - Andrej Karpathy
Comments
Post a Comment