add file

3-drafting/beyond-vibe-coding.md

@@ -2,9 +2,11 @@
 slug: beyond-vibe-coding
 title: "Beyond Vibe Coding: Professional AI Development Methodologies"
 author: henry-technical
-status: drafting
+status: published-part1
 created: 2026-01-22
-updated: 2026-01-24
+updated: 2026-02-02
+published_p1: 2026-02-02
+published_url_p1: https://dev.to/h1gbosn/what-is-vibe-coding-in-2026-one-year-from-karpathys-tweet-5f43
 content_type: explainer
 primary_keyword: "ai coding methodologies"
 secondary_keywords: ["spec driven development", "ai pair programming", "human in the loop ai", "ralph loop"]
@@ -25,7 +27,7 @@ assets_folder: assets/beyond-vibe-coding/
 
 # Brief
 
-See [brief.md](assets/beyond-vibe-coding/brief.md) for complete strategic context, target reader analysis, content requirements, and success criteria.
+See [brief.md](assets/beyond-vibe-coding/brief.md)
 
 **Quick Summary:**
 - **Goal:** Fight "AI is for juniors" stigma with data-backed professional methodologies survey
@@ -37,120 +39,137 @@ See [brief.md](assets/beyond-vibe-coding/brief.md) for complete strategic contex
 
 # Outline
 
-See [outline.md](assets/beyond-vibe-coding/outline.md) for complete article structure.
+See [outline.md](assets/beyond-vibe-coding/outline.md)
 
 **Tone:** "Here's what exists and here's what I actually do" — landscape survey through practitioner's lens, not prescriptive guide
 
-**Structure:**
-- Introduction (400w) — Hook with vibe coding, establish legitimacy question
-- 6 Methodology sections (400-500w each) — Credentials block, description, Henry's experience (integrated naturally)
-- Conclusion (450w) — Landscape overview, legitimacy validation with stats, what I use, community invitation
-
-**Total:** ~2,800 words
-**Code examples:** 3 (CLAUDE.md spec, .claude/settings.json, TDD test)
-
 ---
 
-# Validation Status
+# Validation Results
 
 **Validated:** 2026-01-23
 **Validator:** @validator
-**Verdict:** REVISE → COMPLETE ✅
+**Verdict:** PASS (after revisions)
 
-See [validation-results.md](assets/beyond-vibe-coding/validation-results.md) for complete validation report.
+See [validation-results.md](assets/beyond-vibe-coding/validation-results.md)
 
 **Summary:**
-- ✅ **4 claims fully verified:** Senior/junior AI usage, 76% adoption, 27% bans, Ralph Loop virality
+- 4 claims fully verified: Senior/junior AI usage, 76% adoption, 27% bans, Ralph Loop virality
-- ✅ **Security vulnerabilities claim updated:** Added source citations [1][2][3]
+- Security vulnerabilities claim updated with source citations
-- ✅ **Removed false claims:** "359x growth" for SDD, "90% Fortune 100 Copilot adoption"
+- Removed false claims: "359x growth" for SDD, "90% Fortune 100 Copilot adoption"
-- ✅ **Minor stat correction:** "33%" → "about a third" for senior developers
+- Minor stat correction: "33%" → "about a third"
-
-**Revisions Applied by @architect:**
-1. Removed Claim 4 (90% Fortune 100) from Conclusion section
-2. Removed Claim 6 (359x growth) from Spec-Driven credentials, replaced with qualitative description
-3. Added source citations for Claim 3 (security vulnerabilities): Georgetown CSET, Veracode, industry reports
-4. Updated Claim 1 to "about a third" instead of "33%" in Introduction and Conclusion
-
-**Next Step:** Ready for @writer to create Draft
 
 ---
 
-# Assets Index
+# Text
 
-All working files for this article:
+**Format:** 3-part series for dev.to
 
-## Core Files
+| Part | File | Title | Status |
+|------|------|-------|--------|
+| 1 | [text-p1.md](assets/beyond-vibe-coding/text-p1.md) | What Is Vibe Coding in 2026? One Year From Karpathy's Tweet | **Published** [dev.to](https://dev.to/h1gbosn/what-is-vibe-coding-in-2026-one-year-from-karpathys-tweet-5f43) |
+| 2 | [text-p2.md](assets/beyond-vibe-coding/text-p2.md) | AI Pair Programming vs Agentic Coding | Ready |
+| 3 | [text-p3.md](assets/beyond-vibe-coding/text-p3.md) | Human-in-the-Loop + TDD + AI | Ready |
 
-| File | Purpose | Status |
+**Reference:** [text.md](assets/beyond-vibe-coding/text.md) — original monolithic version before split
-|------|---------|--------|
-| [brief.md](assets/beyond-vibe-coding/brief.md) | Complete Brief: strategic context, target reader, requirements, success criteria | ✅ Complete |
-| [outline.md](assets/beyond-vibe-coding/outline.md) | Article structure with word budgets | ✅ Revised & Complete |
-| [text.md](assets/beyond-vibe-coding/text.md) | Article draft (English) | ✅ Draft complete |
-| [text-rus.md](assets/beyond-vibe-coding/text-rus.md) | Article draft (Russian) | ✅ Complete |
-| [interview.md](assets/beyond-vibe-coding/interview.md) | Oleg's practitioner insights — source for Henry's voice | ✅ Complete |
-| [log-chat.md](assets/beyond-vibe-coding/log-chat.md) | Activity log and agent comments | ⏳ Active |
-| [seo-metadata.md](assets/beyond-vibe-coding/seo-metadata.md) | SEO title, description, keywords | ⏳ Pending @seo |
 
-## Methodology Specs
+**Russian version:** [text-rus.md](assets/beyond-vibe-coding/text-rus.md)
-
-Detailed research for each methodology — use for expanding credentials in text.md:
-
-| File | Methodology | Key Sources |
-|------|-------------|-------------|
-| [spec-driven-dev.md](assets/beyond-vibe-coding/spec-driven-dev.md) | Spec-Driven Development | GitHub Spec Kit, AWS Kiro, Tessl, Martin Fowler |
-| [agentic-coding.md](assets/beyond-vibe-coding/agentic-coding.md) | Agentic Coding + Ralph Loop | arXiv papers, Geoffrey Huntley, Cursor 2.0, GitHub Copilot Agent Mode |
-| [ai-pair-programming.md](assets/beyond-vibe-coding/ai-pair-programming.md) | AI Pair Programming | GitHub Copilot official, Microsoft Learn, Cursor, Windsurf |
-| [ai-aided-test-first.md](assets/beyond-vibe-coding/ai-aided-test-first.md) | TDD + AI | Thoughtworks Radar, Kent Beck, DORA Report 2025, Builder.io |
-
-## Statistics & Research
-
-| File | Purpose | Status |
-|------|---------|--------|
-| [ai-usage-statistics.md](assets/beyond-vibe-coding/ai-usage-statistics.md) | Statistical research: AI adoption by seniority, company policies, security concerns | ✅ Complete |
-| [ai-adoption-statistics.md](assets/beyond-vibe-coding/ai-adoption-statistics.md) | LaTeX-formatted statistics for infographics (2024-2026 data) | ✅ Complete |
-| [research-index.md](assets/beyond-vibe-coding/research-index.md) | Methodology clusters, verified sources, interview questions | ⏳ Needs update |
-| [validation-results.md](assets/beyond-vibe-coding/validation-results.md) | Fact-checking results for all statistical claims | ✅ Complete |
-
-## Images
-
-| Folder | Contents | Status |
-|--------|----------|--------|
-| [images/comic/](assets/beyond-vibe-coding/images/comic/) | 8 comic illustrations, uploaded to CDN | ✅ Ready |
-| [images/infographic/](assets/beyond-vibe-coding/images/infographic/) | Infographics (based on ai-adoption-statistics.md) | ⏳ In progress |
-| [images/comic/cdn-urls.md](assets/beyond-vibe-coding/images/comic/cdn-urls.md) | CDN URLs for all comic images | ✅ Complete |
-
-## External Research
-
-| File | Purpose |
-|------|---------|
-| [perplexity-chats/AI-Assisted Development_...](research/perplexity-chats/) | Original Perplexity research on terminology |
 
 ---
 
-# TODO: Part 4 (Potential Future Addition)
+# SEO Optimization
 
-Consider adding a fourth part to the series covering additional methodologies:
+See [seo-metadata.md](assets/beyond-vibe-coding/seo-metadata.md) (pending completion)
 
-| Methodology | Description | Status |
+**Strategy (from @seo research):**
-|-------------|-------------|--------|
-| Architecture-First AI Development | Design patterns and system architecture before AI implementation | ⏳ Needs research |
-| Prompt-Driven Development | Structured prompt engineering as development methodology | ⏳ Needs research |
-| Copy-pasting from AI chatbot | Manual workflow — baseline to compare other methods against | ⏳ Needs research |
 
-**Rationale:** These approaches represent common patterns not covered in Parts 1-3:
+| Keyword | Volume | Notes |
-- Architecture-First — enterprise/complex systems angle
+|---------|--------|-------|
-- Prompt-Driven — bridges gap between vibe coding and spec-driven
+| vibe coding | 90,500 | Primary umbrella |
-- Copy-pasting — the "default" many developers start with, important baseline
+| what is vibe coding | 40,500 | Part 1 hook |
+| spec driven development | 1,300 | Explosive growth |
+| ai pair programming | 720 | Part 2 target |
+| human in the loop ai | 880 | Part 3 target |
 
-**Next steps:**
+**Publication timing:** Part 1 on Feb 2, 2026 — exact 1-year anniversary of Karpathy's tweet.
-1. Research each methodology for credentials and sources
+
-2. Conduct interview with Oleg for Henry's perspective
+---
-3. Assess if volume/interest justifies a Part 4
+
+# Image Specs
+
+See [images/comic/cdn-urls.md](assets/beyond-vibe-coding/images/comic/cdn-urls.md)
+
+**Status:** 8 comics + 2 infographics uploaded to CDN
+
+| Type | Count | Location |
+|------|-------|----------|
+| Comics | 8 | images/comic/ |
+| Infographics | 2 | images/infographic/ |
+| Hero | 1 | images/hero-image.jpeg |
+
+**Pending:** robots-flesh-bag-comic (HITL section)
+
+---
+
+# Review Chat
+
+## 2026-02-02 @user + @editor — Part 1 Publication
+
+**Published:** https://dev.to/h1gbosn/what-is-vibe-coding-in-2026-one-year-from-karpathys-tweet-5f43
+
+**Human edits before publication:**
+- Removed H1 title (dev.to handles separately)
+- "started it all" → "started it" (more measured)
+- Removed "(or 'vibecoding' as some write it)"
+- Added infographic: "Vibe Coding DO and DON'T"
+
+**Voice concern:** Article became more formal after SEO optimization. Need to restore Henry's personal voice in Parts 2-3.
 
 ---
 
 # Activity Log
 
-See [log-chat.md](assets/beyond-vibe-coding/log-chat.md)
+See [log-chat.md](assets/beyond-vibe-coding/log-chat.md) for complete history.
 
-**Latest:** @writer completed draft (2026-01-24). 2,650 words, 8 image placeholders for @image agent. No code snippets per user request.
+**Key milestones:**
+
+| Date | Agent | Action |
+|------|-------|--------|
+| 2026-01-22 | @strategist | Initial setup, research, interview |
+| 2026-01-22 | @strategist | Keyword research, Brief creation |
+| 2026-01-23 | @strategist | Brief refinements (impostor syndrome angle) |
+| 2026-01-23 | @architect | Outline creation |
+| 2026-01-23 | @validator | Fact-checking, removed false claims |
+| 2026-01-24 | @writer | Draft creation (text.md) |
+| 2026-01-31 | @seo | Series split (3 parts), keyword optimization |
+| 2026-02-01 | @writer | Split into text-p1/p2/p3.md, expanded credentials |
+| 2026-02-02 | @user | Part 1 published on dev.to |
+
+---
+
+# TODO: Part 4 (Future)
+
+Consider adding a fourth part covering additional methodologies:
+
+| Methodology | Description | Status |
+|-------------|-------------|--------|
+| Architecture-First AI Development | Design patterns and system architecture before AI implementation | Needs research |
+| Prompt-Driven Development | Structured prompt engineering as development methodology | Needs research |
+| Copy-pasting from AI chatbot | Manual workflow — baseline to compare other methods against | Needs research |
+
+---
+
+# Research Files
+
+| File | Purpose |
+|------|---------|
+| [interview.md](assets/beyond-vibe-coding/interview.md) | Oleg's practitioner insights — source for Henry's voice |
+| [ai-usage-statistics.md](assets/beyond-vibe-coding/ai-usage-statistics.md) | Statistical research for claims |
+| [ai-adoption-statistics.md](assets/beyond-vibe-coding/ai-adoption-statistics.md) | LaTeX-formatted stats for infographics |
+| [research-index.md](assets/beyond-vibe-coding/research-index.md) | Source verification index |
+
+**Methodology specs:**
+- [spec-driven-dev.md](assets/beyond-vibe-coding/spec-driven-dev.md)
+- [agentic-coding.md](assets/beyond-vibe-coding/agentic-coding.md)
+- [ai-pair-programming.md](assets/beyond-vibe-coding/ai-pair-programming.md)
+- [ai-aided-test-first.md](assets/beyond-vibe-coding/ai-aided-test-first.md)

assets/beyond-vibe-coding/log-chat.md

@@ -646,3 +646,28 @@ Rationale:
 
 ---
 
+## 2026-02-02 @user + @editor — Part 1 Published
+
+**Action:** Publication + final human edits
+
+**Published:**
+- URL: https://dev.to/h1gbosn/what-is-vibe-coding-in-2026-one-year-from-karpathys-tweet-5f43
+- Date: February 2, 2026 (exact 1-year anniversary of Karpathy's tweet)
+
+**Human edits before/after publication:**
+- Removed H1 title (dev.to handles separately)
+- Removed "Part 1 of series" subtitle
+- "started it all" → "started it" (more measured)
+- Removed "(or 'vibecoding' as some write it)" — simplified
+- "But be honest:" → "Let's be honest:" — softer invitation
+- Changed intro ending from "my main approach for serious projects" to "then we will go through other approaches in follow up parts"
+- Added new infographic: "Vibe Coding DO and DON'T"
+
+**Voice concern raised:**
+User concerned article became "more formal and robotic" after SEO optimization. Lost original direction: showing best practices beyond vibe coding + Henry's personal experience.
+
+**@editor analysis:**
+See discussion below in log.
+
+---
+

assets/beyond-vibe-coding/sdd-vs-vibe.md

@@ -0,0 +1,266 @@
+# Spec-Driven Development: Решение проблем Vibe Coding
+
+## Определение SDD
+
+Spec-Driven Development — методология AI-разработки, где детальные спецификации создаются до написания кода и служат единственным источником истины для AI-агентов. Workflow: Constitution → Requirements → Design → Tasks → Implementation.
+
+## Проблемы Vibe Coding и решения через SDD
+
+### 1. Context Amnesia
+**Проблема Vibe**: Потеря контекста после ~30 промптов, 40-60% времени на повторное объяснение контекста.
+**Решение SDD**: Спецификации как persistent storage контекста. Контекст доставляется один раз, 80%+ успех с первой попытки.
+
+### 2. Production Readiness
+**Проблема Vibe**: 
+- Только 9% разработчиков готовы деплоить vibe-код в production
+- 63% тратят БОЛЬШЕ времени на дебаг AI-кода
+- 68% тратят БОЛЬШЕ времени на устранение уязвимостей
+- 170/1,645 приложений Lovable имели security vulnerabilities
+
+**Решение SDD**: 
+- 65%+ confidence для production deployment
+- Testability: 4-5/5 vs 2-4/5 у vibe
+- Scalability: 4/5 vs 2-3/5 у vibe
+- Diagnosability: 4/5 vs 2/5 у vibe
+
+### 3. Intent-to-Implementation Deviation
+**Проблема Vibe**: Накопление отклонений от изначального намерения с каждой итерацией. Кодовая база дрейфует.
+**Решение SDD**: Спецификация как source of truth фиксирует намерение. Каждая итерация валидируется против spec.
+
+### 4. Team Collaboration
+**Проблема Vibe**: Вся история в chat logs, невозможность onboarding новых членов команды.
+**Решение SDD**: 
+- Specs в version control (git)
+- Документированные решения и обоснования
+- Onboarding новых членов за минуты vs часы/дни
+
+### 5. Maintainability
+**Проблема Vibe**: 
+- Отсутствие документации
+- Зависимость от AI для каждого технического вызова
+- "Создает разработчиков, которые не способны заниматься maintenance"
+
+**Решение SDD**: 
+- Specs как живая документация
+- Maintainability score: 4/5 vs 2-3/5 у vibe
+- Четкая структура для code review
+
+### 6. Скорость vs Качество
+**Проблема Vibe**: 19% МЕДЛЕННЕЕ реально, хотя ощущается 20% быстрее (METR study).
+**Решение SDD**: Медленнее upfront, но минимум rework. Общий cycle time короче для production-ready кода.
+
+## Статистика использования SDD
+
+### Adoption Rate
+- **84%** разработчиков используют AI-инструменты (общий рынок)
+- **~60-70%** переходят на гибридный подход Vibe+SDD после 6+ месяцев
+- **~20-25%** внедрили полностью SDD-workflow для всех production-задач
+- **20-50%** кода в Robinhood и Microsoft генерируется через SDD-подходы
+
+### Timeline и Tools
+- **Сентябрь 2025**: Запуск GitHub Spec-Kit (open source)
+- **Июль 2025**: Запуск AWS Kiro IDE
+- **2025**: SDD становится key engineering practice (Thoughtworks Technology Radar)
+
+### Распределение по опыту
+- **Senior (10+ лет)**: Преимущественно используют SDD для production, 81% productivity gain
+- **Mid-level (3-10 лет)**: Смешанное использование, переход на SDD для сложных проектов
+- **Junior (0-3 лет)**: Редко используют SDD из-за сложности написания качественных specs
+
+### Industry Adoption
+- Tech Startups: 73% adoption AI-tools (часть через SDD)
+- Digital Agencies: 61%
+- E-commerce: 57%
+
+## Достоинства перехода Vibe → SDD
+
+### Количественные метрики
+
+| Метрика | Vibe Coding | SDD | Улучшение |
+|---------|-------------|-----|-----------|
+| Production Confidence | 9% | 65%+ | +622% |
+| Context Re-explanation Time | 40-60% | <10% | -80% |
+| First-try Success Rate | ~40% | 80%+ | +100% |
+| Testability | 2-4/5 | 4-5/5 | +50% |
+| Maintainability | 2-3/5 | 4/5 | +60% |
+| Diagnosability | 2/5 | 4/5 | +100% |
+| Team Onboarding Time | Часы/дни | Минуты | -90% |
+
+### Качественные преимущества
+
+**1. Улучшенная переиспользуемость**
+- Research logs и specs документируют решения
+- Снижение дублирования кода
+- Knowledge base для команды
+
+**2. Минимизация потери контекста**
+- Git-committed specs сохраняют всю историю
+- Не зависит от chat history limits
+- Specs переживают AI sessions
+
+**3. Упрощенный code review**
+- Валидация против specs
+- Четкие acceptance criteria
+- Автоматизированные проверки соответствия
+
+**4. Predictable outcomes**
+- Specs определяют "done"
+- Минимум неопределенности
+- Ясные expectations для AI
+
+**5. Scalable architecture**
+- Specs форсируют думать о структуре
+- Architectural decisions документируются
+- Prevents ad-hoc solutions
+
+### Экономические преимущества
+
+**Снижение costs**:
+- Меньше времени на rework (40-60% → <10%)
+- Меньше debugging time (63% excess → minimal)
+- Меньше security vulnerabilities (68% excess time → early detection)
+
+**Увеличение velocity**:
+- Быстрее onboarding ($X/hour * hours saved)
+- Параллельная работа команды (specs как contract)
+- Reusable specs для похожих features
+
+## SDD Tooling Ecosystem
+
+### Major Platforms
+
+**1. GitHub Spec-Kit** (сентябрь 2025)
+- CLI + templates
+- Commands: `/constitution`, `/specify`, `/plan`, `/tasks`, `/implement`
+- Интеграция: Cursor, Copilot, Claude Code, Windsurf
+- Open source, активное community
+
+**2. AWS Kiro** (июль 2025)
+- Dedicated IDE (VS Code fork)
+- Spec Mode + Vibe Mode
+- Files: `requirements.md`, `design.md`, `tasks.md`
+- Context management через structured files
+
+**3. OpenSpec**
+- Lightweight alternative
+- Markdown-based
+- Files: `proposal.md`, `specs/*.md`, `tasks.md`, `design.md`
+
+**4. Better Spec**
+- AI-powered spec generation
+- Hot module replacement
+- Multi-model support (Claude, GPT-4, Gemini, local)
+
+**5. APM (Windsurf)**
+- Multi-agent система
+- File-based memory
+- CLI workflows
+
+### Agent Integration
+
+**Claude Code**
+- Custom slash commands (`.claudecode/`)
+- `CLAUDE.md` constitution
+- Task spawning, planning mode
+
+**Cursor**
+- Composer Workspace
+- Agent Mode
+- Spec-kit integration via custom commands
+- `.cursorrules` customization
+
+**Windsurf**
+- Cascade context system
+- APM framework
+- Multi-model support
+
+**VS Code + GitHub Copilot**
+- Custom instructions via markdown
+- Spec templates auto-completion
+- API contract generation (OpenAPI/Swagger)
+
+**Rovo (Atlassian)**
+- Integrated spec management
+- Jira synchronization
+- Team collaboration features
+
+### Common Workflow
+
+```
+1. /constitution → project principles & constraints
+2. /specify → user stories & requirements  
+3. /plan → technical design & architecture
+4. /tasks → granular task breakdown
+5. /implement → code generation against specs
+6. Iterate: /clarify для edge cases
+```
+
+## Use Cases для SDD
+
+### Оптимально
+- Production systems для customers
+- Enterprise applications с compliance
+- Team collaboration (>2 developers)
+- Long-lived codebases
+- Complex architectures (microservices)
+- Mission-critical systems
+
+### Не оптимально
+- Disposable prototypes
+- Solo pet projects без maintenance
+- Сверх-простые скрипты
+- High uncertainty exploration phase
+
+## Hybrid Approach: Лучшая практика
+
+**Рекомендованная стратегия** (60-70% developers):
+
+1. **Exploration (Phase 0)**: Vibe coding для PoC (1-3 дня)
+2. **Development (Phase 1-N)**: SDD для core features при validation идеи
+3. **Maintenance**: SDD для features, vibe для minor fixes
+
+**Ключевой принцип**: "Vibe coding — как вы исследуете AI. Spec-Driven Development — как вы выпускаете продукт с AI."
+
+## Key Insights
+
+### Паттерны переходов
+- **Vibe → SDD**: Доминирующий паттерн (~70% после 6+ мес)
+- **Триггеры перехода**: Барьер ~30 промптов, production requirements, team growth
+- **Spec → Vibe**: Практически не встречается
+
+### По типам задач
+SDD особенно эффективен для:
+- Complex business logic (34% AI gain без SDD)
+- Security-critical code (12% AI gain без SDD)  
+- Multi-service architectures
+- Long-term projects (>3 months)
+
+### Эволюция подхода
+- 2024-early 2025: Vibe coding доминирует
+- Mid-2025: SDD tools запускаются (Kiro, Spec-Kit)
+- Late 2025-2026: Hybrid становится стандартом
+- Future: Спецификации как executable artifacts
+
+## Цитаты экспертов
+
+**На тему production-готовности**:
+"Production-grade качество требует преднамеренного надзора. Testability, maintainability, scalability заметно улучшились, когда были усилены через промпты, тестовые стратегии и ревью." — Thoughtworks
+
+**На тему context management**:
+"Pure vibe coding: 40-60% времени на повторное объяснение контекста. Spec-Driven: Контекст доставлен один раз, 80%+ первоначальный успех."
+
+**На тему философии**:
+"Vibe coding принимает отклонение как стоимость скорости. SDD минимизирует отклонение через upfront structure."
+
+## Источники
+
+- GitHub Spec-Kit documentation & repository (2025-09)
+- AWS Kiro launch materials (2025-07)  
+- Thoughtworks Technology Radar 2025
+- RedMonk developer surveys (2025)
+- Visual Development Survey 2025
+- Reddit communities: r/ClaudeCode, r/ChatGPTCoding, r/windsurf
+- Business Insider: 167 developers survey (2026-01)
+- METR study on AI coding performance
+- Second Talent: Vibe Coding Statistics 2026
+- Lovable vulnerability analysis (170/1,645 apps)

assets/beyond-vibe-coding/text-p1.md

@@ -1,24 +1,20 @@
-# What Is Vibe Coding in 2026? One Year From Karpathy's Tweet
+What is vibe coding in 2026? Exactly one year ago — February 2, 2025 — Andrej Karpathy posted the tweet that started it. But here's the thing: what Karpathy meant and what "vibe coding" means now are two different things.
-
-*Part 1 of the "Beyond Vibe Coding" series*
-
-What is vibe coding in 2026? Exactly one year ago — February 2, 2025 — Andrej Karpathy posted the tweet that started it all. The term became Collins Dictionary's Word of the Year. But here's the thing: what Karpathy meant and what "vibe coding" (or "vibecoding" as some write it) means now are two different things.
 
 {% embed https://x.com/karpathy/status/1886192184808149383 %}
 
-When Karpathy first used the term, he meant something specific. You tell the agent what to do and evaluate the result. The key "vibe" is that you don't dig into HOW the code is written. Something doesn't work? Just write the next prompt, and so on. Now "vibe coding" often means any AI-assisted development at all. Though honestly — in many cases, that's exactly how it works.
+When Andrej Karpathy first used the term, he meant something specific. You tell the agent what to do and evaluate the result. The key "vibe" is that you don't dig into HOW the code is written. Something doesn't work? Just write the next prompt, and so on.
 
-We're already seeing derivatives — vibe design, vibe ops, vibe anything. But professional developers need more than vibes. That's where approaches like spec-driven development come in — and that's what this series is about.
+Now "vibe coding" often means any AI-assisted development at all. Though honestly — in many cases, that's exactly how it works. We're already seeing derivatives — vibe design, vibe ops, vibe anything. But professional developers need more than vibes. That's where approaches like spec-driven development come in — and that's what this series is about.
 
 ![Comic: Senior developer explains you need to understand code first, junior admits he builds first then figures out structure](https://cdn.banatie.app/blog/henry-devto/img/c0c3ad3d-13ee-4dbf-9f4a-5db3bf64b378)
 
-But be honest: when you accept the agent's changes without looking, you catch yourself thinking — is this actually done right, can I trust what the LLM generated without reviewing it? When a colleague says they vibe-coded some functionality — do you picture thoughtful architecture or more like "somehow works"? Is vibe coding cheating and irresponsibility, or a perfectly professional approach?
+Let's be honest: when you accept the agent's changes without looking, you catch yourself thinking — is this actually done right, can I trust what the LLM generated without reviewing it? When a colleague says they vibe-coded some functionality — do you picture thoughtful architecture or more like "somehow works"? Is vibe coding cheating and irresponsibility, or a perfectly professional approach?
 
 What I know for certain — AI development is here, whatever we call it. According to Stack Overflow 2024, 76% of developers use or plan to use AI tools. About a third of senior developers — those with 10+ years of experience — generate more than half their code with AI.
 
 ![Infographic: AI adoption among developers - 76% use AI tools, productivity and trust metrics](https://cdn.banatie.app/blog/henry-devto/img/1175042e-1e41-4675-8fb3-25febe7cedea)
 
-Let's figure out what exactly we can do with AI. Different approaches exist, giving more control at different stages of work. Choosing the right one and applying it consciously — that's the professional approach. In this article, I'll cover vibe coding itself and spec-driven development — my main approach for serious projects.
+Here's what's out there — and what I actually use. Different approaches exist, giving more control at different stages of work. The point is knowing when to use which. In this article, I'll cover vibe coding itself and spec-driven development — then we'll go through other approaches in follow-up parts.
 
 ---
 
@@ -52,7 +48,7 @@ Be careful with security. Don't use vibe coding on critical infrastructure. Espe
 
 ![Infographic: Vibe Coding DO and DON'T - when to use and when to avoid](https://cdn.banatie.app/blog/henry-devto/img/c5735016-326f-48f6-b8b7-cb35890739a8)
 
-You might ask — is it even legitimate to use vibe coding at work? Absolutely! First, you save significant energy on simple things. Your brain resources are limited — delegate simple tasks and routine to AI. It'll do it faster, and you can spend your focus on more important stuff. Second, techniques exist beyond vibe coding that significantly improve development quality and reliability.
+You might ask — is it even legitimate to use vibe coding at work? Absolutely! First, you only have so much attention in a day. I'd rather save my focus for the hard stuff — and delegate simple tasks and routine to AI. It'll do it faster anyway. Second, techniques exist beyond vibe coding that significantly improve development quality and reliability.
 
 So what are these methods?
 
@@ -73,7 +69,7 @@ So what are these methods?
 
 Write detailed specification BEFORE code. Spec includes requirements, architecture, API contracts, error handling, edge cases. AI executes against the spec. The spec becomes living documentation — often saved as `CLAUDE.md` or `.spec` files in project root.
 
-Human focuses on WHAT. AI handles HOW.
+You decide WHAT to build, define the STRUCTURE, go as deep as you need. AI carefully handles the implementation.
 
 This is actually my main approach for large projects. Especially when adding a new section or functionality that didn't exist before. Time spent writing spec is often significant. But it gives good control — modern models follow instructions pretty well. You can vary the degree of freedom for the agent: you can specify file and folder names yourself, or just give an outline of the solution.
 
@@ -101,7 +97,7 @@ In Part 2, we'll explore the autonomy spectrum: AI pair programming (where you s
 
 In Part 3: Human-in-the-Loop patterns and TDD + AI — when you need guardrails and quality guarantees.
 
-Different approaches for different stakes. Choose consciously.
+No single right answer — pick what fits the situation.
 
 ---