# AI-assisted coding -\> Vibe Engineering \<- Vibe Coding

DevFeed: [AI-assisted coding -\> Vibe Engineering \<- Vibe Coding](<https://devfeed.tech/articles/ai-assisted-coding-vibe-engineering-vibe-coding-25354.md>)

Original publisher: [Read original article](<https://kau.sh/blog/vibe-eng/>)

Author: Kaushik Gopal

Published: 2025-11-18T00:00:00Z

Content type: opinion

Language: en

Sources: [Kaushik Gopal's Site](<https://devfeed.tech/sources/kaushik-gopal-s-site.md>)

Topics: [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Vibe coding](<https://devfeed.tech/topics/vibe-coding.md>), [coding](<https://devfeed.tech/topics/coding.md>), [cursor](<https://devfeed.tech/topics/cursor.md>), [GitHub Copilot](<https://devfeed.tech/topics/github-copilot.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>)

Tags: [ai-assisted-coding](<https://devfeed.tech/tags/ai-assisted-coding.md>), [bash](<https://devfeed.tech/tags/bash.md>), [code](<https://devfeed.tech/tags/code.md>), [coding](<https://devfeed.tech/tags/coding.md>), [cross-platform](<https://devfeed.tech/tags/cross-platform.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [github-copilot](<https://devfeed.tech/tags/github-copilot.md>), [go](<https://devfeed.tech/tags/go.md>), [vibe-coding](<https://devfeed.tech/tags/vibe-coding.md>)

## AI overview

The article distinguishes AI-assisted coding, vibe coding, and vibe engineering by who generates most of the code and who owns the design and quality bar. It presents AI-assisted coding as programmer-led autocomplete, while warning that vibe coding can produce poorly understood code as codebases grow and require maintenance.

## Source excerpt

We're still wrestling with how much AI belongs in our day to day coding. Three phrases keep getting mixed together: AI-assisted coding Vibe coding Vibe engineering These are not the same. AI Assisted Vibe coding Vibe engineering Generates the code 👨💻 (+ 🤖) 🤖 🤖 Owns the design 👨💻 ︎🤖 👨💻 ︎ They differ along two dimensions: who generates most of the code and who owns the design and quality bar. 1. AI-assisted coding ## This is where we started. You, the programmer, write most of the code. AI acts as super-powered autocomplete. You type most of the code yourself. AI handles completions, boilerplate, pieces of the logic and maybe small refactors. Your eyes stay on every line, and the AI rarely acts without you explicitly placing or accepting a suggestion. This is still "you drive, AI rides shotgun". GitHub Copilot was the early poster child. Here's an early video of me dabbling with Copilot and scripts. Today, Cursor Tab has taken the crown: fast, inline help without giving up control of the codebase. I particularly like how accurate Cursor is at predicting the next point of code entry or edit. When it works well, it disappears into the background and silently increases your productivity. Get it wrong, and you're immediately frustrated with AI. 2. Vibe coding ## This took the world by storm. AI generates most if not all of the code. You, the programmer, react with feedback in English and are not as in tune with what the actual code shapes up to be. You give up intentional design. In practice, you're letting the model make the architectural calls: file structure, abstractions, naming, everything. As your codebase grows and needs ongoing maintenance, vibe coding breaks down. Your code turns into mystery-meat: it runs, but nobody understands clearly how or why. This is why experienced greybeards raise alarms and complain about AI bots on their lawns. But Vibe coding does shine in a few scenarios: Non-programmers who need something working without caring about internals Fa