Vibe work / Standard term
AI pair programming
A coding workflow where the AI suggests changes, autocompletes functions, and generates boilerplate while the human developer drives decisions, reviews every meaningful line, and stays accountable for the result.
AI pair programming is a coding workflow where the AI suggests changes, autocompletes functions, and generates boilerplate while the human developer drives decisions, reviews every meaningful line, and stays accountable for the result. The developer reads, understands, tests, and accepts or rejects each suggestion. Someone working this way might accept an AI-generated sort function, read through it to confirm correctness, write a test, and move on. The AI handles mechanical work; the human handles judgment and ownership. GitHub Copilot popularized this model starting in 2021.
Builder example
For teams shipping production software, AI pair programming provides a pragmatic middle ground. Developers move faster on boilerplate, exploration, and test writing while maintaining the code understanding and review habits that keep systems maintainable. It works as a default norm because it preserves accountability.
A developer asks Copilot or another assistant to draft a parser, then steps through edge cases and tests the output.
The AI accelerates the draft. The human checks the contract, data shape, and failure behavior.
Common confusion: What separates this from vibe coding is ownership. In AI pair programming, the developer understands and can defend every line that ships. In vibe coding, the developer accepts code they have not fully read or understood.