vibe-coding: light update

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"]

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/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.
 
 ---