# vibe-coding-vs-ai-assisted-engineering-osmani-2025-11-01

## Veille

Vibe coding vs AI-assisted engineering - Addy Osmani - Software development - Engineering principles - LinkedIn

## Titre Article

Vibe-coding is not the same as AI-Assisted engineering.

## Date

2025-11-01

## URL

https://www.linkedin.com/posts/addyosmani_ai-programming-softwareengineering-activity-7368168236628013056-y20E

## Keywords

ai, programming, softwareengineering, vibe coding, AI-assisted engineering, software development, prototypes, MVPs, test-driven development, code reviews, engineering principles, force multiplier, human engineer control, scalability, maintainability, technical debt

## Authors

Addy Osmani

## Ton

**Profil:** Professionnel | Première personne autorité | Opinion-Éducative | Intermédiaire-Accessible

Osmani adopte le ton d'un senior engineer faisant une mise en garde professionnelle. Son argumentation ("devalues engineering discipline", "misleads newcomers") révèle une opinion forte mais pédagogique. Le langage reste accessible ("throwaway weekend projects") tout en maintenant rigueur technique. Typique des thought leaders tech sur LinkedIn combinant autorité professionnelle et accessibilité.

## Pense-betes

- **Crucial distinction**: "vibe coding" ≠ "AI-assisted engineering"
- **Vibe Coding**: high-level prompting, creative flow, rapid experimentation; ideal for prototypes, MVPs, learning and "throwaway weekend projects"; less rigorous code review
- **AI-Assisted Engineering**: methodical integration of AI into a mature development lifecycle (SDLC); AI acts as a "force multiplier" for boilerplate and tests; the human engineer retains control of architecture and review; ensures a secure, scalable and maintainable product
- **FAANG team**: **+30% development speed** through disciplined augmentation (cited Reddit post)
- **Risks of confusion**: devalues engineering skill and rigor, gives beginners the false impression that production can be reached through simple prompting
- **Best practices**: start from a solid design, subject all AI code to rigorous human review, treat AI as a powerful tool rather than a replacement
- **AI as a junior developer**: "helpful, but never without supervision"
- **Verification burden**: significant oversight is required to prevent technical debt, security vulnerabilities and maintainability issues
- **Redefined technical autonomy**: understanding *when*, *what* and *why* to code, not just *how*

## RésuméDe400mots

Addy Osmani's LinkedIn post, titled "Vibe-coding is not the same as AI-Assisted engineering", addresses a **critical semantic distinction** in the rapidly evolving software development landscape. Osmani argues that conflating "vibe coding" with professional "AI-assisted engineering" risks **devaluing engineering discipline** and giving newcomers an incomplete picture of what building robust, production-ready software actually requires.

**Defining Vibe Coding**

He defines **"vibe coding"** as a highly creative, fluid approach where developers interact with AI through high-level prompting, often accepting suggestions without thorough review. This method prioritizes speed and iterative experimentation, making it ideal for generating prototypes, MVPs, learning exercises, or **"throwaway weekend projects"**. It is a powerful way to build intuition and flatten the learning curve for beginners, favoring exploration over the correctness and maintainability essential to professional applications.

**AI-Assisted Engineering: the disciplined approach**

In sharp contrast, **"AI-assisted engineering"** is presented as the methodical integration of AI into a mature software development lifecycle. Here, AI functions as a **"force multiplier"**, assisting engineers with tasks such as boilerplate generation or drafting test cases. Crucially: **the human engineer retains full control and responsibility** for architecture, meticulously reviewing and understanding every line of AI-generated code. This approach ensures a secure, scalable and maintainable final product, augmenting existing solid processes rather than replacing them. A **30% increase in development speed** reported at a FAANG team, cited in a Reddit post that sparked the discussion, is attributed to this disciplined augmentation, not to abandoning engineering principles.

**Risks and distortion**

Osmani warns that **labeling disciplined, AI-augmented workflows as "vibe coding" distorts the skill and rigor** of the engineering profession. For newcomers to the field, this **fuels the dangerous illusion** that one can simply "prompt" one's way to a viable product without any foundational understanding of code or engineering fundamentals.

**Key takeaways and best practices**

The lessons from the post and its comments reinforce the message: **always start from a solid design**, subject any AI-generated code to rigorous human review, and treat AI as an incredibly powerful tool in the engineering toolbox, **not as a magic wand**. As one commenter aptly put it: **"Use AI like a junior developer: helpful, but never without supervision."** The **verification burden** of AI-generated code is significant and demands careful oversight to prevent technical debt, security vulnerabilities and maintainability issues.

**Redefining technical autonomy**

Ultimately, the post argues for a **balanced, informed approach** to AI in software development, where human expertise and established engineering practices remain paramount, leveraging AI to improve productivity within a structured and responsible framework. True **technical autonomy now consists of understanding *when*, *what* and *why* to code**, rather than merely *how* to code.

## GrapheDeConnaissance

- Addy Osmani —affirme_que→ vibe coding ≠ AI-assisted engineering (AFFIRMATION, 0.99)
- Addy Osmani —travaille_chez→ Google Chrome (ORGANISATION, 0.98)
- Vibe Coding —s_applique_à→ prototypes et MVPs (CONCEPT, 0.97)
- AI-Assisted Engineering —utilise→ contrôle humain de l'architecture (CONCEPT, 0.97)
- AI-Assisted Engineering —améliore→ vitesse de développement (CONCEPT, 0.95)
- équipe FAANG —mesure→ 30% d'augmentation de vitesse (MESURE, 0.93)
- Vibe Coding —permet→ dette technique (CONCEPT, 0.9)
- AI-Assisted Engineering —utilise→ IA comme multiplicateur de force (CONCEPT, 0.95)
- Addy Osmani —s_oppose_à→ conflation des deux pratiques (CONCEPT, 0.98)
- Addy Osmani —affirme_que→ l'ingénieur humain conserve la responsabilité de l'architecture (AFFIRMATION, 0.96)
- Addy Osmani —affirme_que→ l'IA est comme un développeur junior, utile mais jamais sans supervision (AFFIRMATION, 0.88)
- Vibe Coding —s_oppose_à→ AI-Assisted Engineering (METHODOLOGIE, 0.97)
- autonomie technique —est_basé_sur→ comprendre quand et pourquoi coder (CONCEPT, 0.91)

---
Canonical: https://www.thekb.eu/en/fiches/vibe-coding-vs-ai-assisted-engineering-osmani-2025-11-01/