Vibe Coding

Stuff everything relevant into context (
AI Readability)

Describe the next single, concrete incremental change we're trying to implement

Don't ask for code, ask for a few high-level approaches, pros/cons.

Pick one approach, ask for first draft code.

Review / learning phase: ask for explanations, clarifications, changes, wind back

Test

Commit

Ask for suggestions on what we could implement next

Repeat

Documentation

LLMs are strong with whiteboarding but weak with improvements

Plan.md

Spec.md

Feedback

Vibe Coding Terminal Editor

I wrote a small tool for myself as my biannual routine check of where llms are currently at. I think I've learned a bunch from this exercise. This is frustrating! I don't want to learn by trial and error, I'd rather read someone's blog post with lessons learned. Sadly, most of the writing on the topic that percolates to me tends to be high-level --- easy to nod along while reading, but hard to extract actionable lessons. So this is what I want to do here, list specific tricks learned.

https://matklad.github.io/2025/08/31/vibe-coding-terminal-editor.html

Andrej Karpathy on Twitter / X

There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. It's possible because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good. Also I just talk to Composer with SuperWhisper…— Andrej Karpathy (@karpathy) February 2, 2025

https://x.com/karpathy/status/1886192184808149383

Vibe Coding Is The Future

Andrej Karpathy recently coined the term “vibe coding” to describe how LLMs are getting so good that devs can simply “give in to the vibes, embrace exponentials, and forget that the code even exists.” We dive into this new way of programming and what it means for builders in the age of AI. Apply to Y Combinator: https://ycombinator.com/apply Chapters (Powered by https://bit.ly/chapterme-yc) - 0:00 Intro 0:42 What is vibe coding? 1:00 What founders in the current YC batch are saying 4:35 Debugging and building systems 6:59 The models people are using now 10:01 What percentage of code is being written by LLM’s? 11:58 What changed and what stayed the same? 18:08 How Triplebyte did candidate assessments and how would that change in this era 21:37 Key skills that will remain relevant 23:01 How do you develop taste without classical training? 30:59 Outro

https://www.youtube.com/watch?v=IACHfKmZMr8

Andrej Karpathy on Twitter / X

Noticing myself adopting a certain rhythm in AI-assisted coding (i.e. code I actually and professionally care about, contrast to vibe code).1. Stuff everything relevant into context (this can take a while in big projects. If the project is small enough just stuff everything…— Andrej Karpathy (@karpathy) April 25, 2025

https://x.com/karpathy/status/1915581920022585597

True no-code

Code is the new no-code

Was I wrong about no-code?

https://lumberjack.so/p/code-is-the-new-no-code

Code Review standards should be differentiated (core code needs thorough review, vibe code only needs to pass tests)

Vibe code isn't meant to be reviewed *

How to stay in control of codebase and not lose vibe code productivity boost. Explicit vibe/human code separation through modular approach

https://monadical.com/posts/vibe-code-how-to-stay-in-control.html

Vibe Coding
Coding Test

old.reddit.com

https://old.reddit.com/r/ProductManagement/comments/1lw9r9h/i_messed_up_my_google_pm_vibe_coding_interview/

Vibe Coding

Documentation

True no-code

Vibe Coding
Coding Test

Backlinks

Recommendations

Vibe Coding

Documentation

True no-code

Vibe Coding Coding Test

Backlinks

Recommendations

Vibe Coding
Coding Test