vibe-coding: images and tweet

This commit is contained in:
Oleg Proskurin 2026-02-01 22:56:00 +07:00
parent 77a6f8bb16
commit 3c0c80588d
2 changed files with 21 additions and 19 deletions

View File

@ -1,13 +1,15 @@
# CDN URLs
| File | URL |
|------|-----|
| ai-tests-autonomous-agent.jpeg | https://cdn.banatie.app/blog/henry-devto/img/94559d7c-06ab-4e5f-860a-87419906f3b5 |
| autonomous-agents-overengineering.jpeg | https://cdn.banatie.app/blog/henry-devto/img/031320e3-9252-4c6a-9c98-e08d7ef40855 |
| autocomplete-suggestions-overload.jpeg | https://cdn.banatie.app/blog/henry-devto/img/8bea3b16-f764-4212-8c09-918b87668884 |
| documentation-prompt-history.jpeg | https://cdn.banatie.app/blog/henry-devto/img/f4800684-adaa-4d22-8ed6-e163ecb55856 |
| karpathy-vibe-coding-tweet.jpeg | https://cdn.banatie.app/blog/henry-devto/img/c4c24f43-d0ac-45d2-84d0-6cb0624a8957 |
| prompt-writing-time-irony.jpeg | https://cdn.banatie.app/blog/henry-devto/img/79c4c6fd-129a-499f-be04-f503eff018b5 |
| understand-code-first-dialog.jpeg | https://cdn.banatie.app/blog/henry-devto/img/c0c3ad3d-13ee-4dbf-9f4a-5db3bf64b378 |
| works-but-dont-understand.jpeg | https://cdn.banatie.app/blog/henry-devto/img/25589837-6cf0-4ee9-bb2f-121ee3edac7d |
| infographic/Generated Image January 31, 2026 - 11_11PM.jpeg | https://cdn.banatie.app/blog/henry-devto/img/1175042e-1e41-4675-8fb3-25febe7cedea |
| File | URL | Used |
|------|-----|------|
| ai-tests-autonomous-agent.jpeg | https://cdn.banatie.app/blog/henry-devto/img/94559d7c-06ab-4e5f-860a-87419906f3b5 | ✓ |
| autonomous-agents-overengineering.jpeg | https://cdn.banatie.app/blog/henry-devto/img/031320e3-9252-4c6a-9c98-e08d7ef40855 | ✓ |
| autocomplete-suggestions-overload.jpeg | https://cdn.banatie.app/blog/henry-devto/img/8bea3b16-f764-4212-8c09-918b87668884 | ✓ |
| documentation-prompt-history.jpeg | https://cdn.banatie.app/blog/henry-devto/img/f4800684-adaa-4d22-8ed6-e163ecb55856 | |
| karpathy-vibe-coding-tweet.jpeg | https://cdn.banatie.app/blog/henry-devto/img/c4c24f43-d0ac-45d2-84d0-6cb0624a8957 | ✓ |
| prompt-writing-time-irony.jpeg | https://cdn.banatie.app/blog/henry-devto/img/79c4c6fd-129a-499f-be04-f503eff018b5 | ✓ |
| understand-code-first-dialog.jpeg | https://cdn.banatie.app/blog/henry-devto/img/c0c3ad3d-13ee-4dbf-9f4a-5db3bf64b378 | ✓ |
| works-but-dont-understand.jpeg | https://cdn.banatie.app/blog/henry-devto/img/25589837-6cf0-4ee9-bb2f-121ee3edac7d | |
| infographic/Generated Image January 31, 2026 - 11_11PM.jpeg | https://cdn.banatie.app/blog/henry-devto/img/1175042e-1e41-4675-8fb3-25febe7cedea | ✓ |
| **DO-DONT-vibe-coding-infographic** | нужно создать | |
| **robots-flesh-bag-comic** | нужно создать | |

View File

@ -2,19 +2,19 @@
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.
https://x.com/karpathy/status/1886192184808149383
{% 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.
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.
[IMAGE: comic. Two developers talking, one young, one older. Young one asks: "Is it true that back in the day you'd understand the code first, then build features?" Older one: "Of course, you need to understand existing code to build a feature. You don't?" Young one: "No, I build the feature first, and only when it fully works do I figure out how the code is structured"]
![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?
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.
[IMAGE: infographic showing AI adoption progress among developers, trust in AI, and productivity metrics]
![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 existing AI development methodologies that I've used in practice, with my honest commentary.
@ -22,7 +22,7 @@ Let's figure out what exactly we can do with AI. Different approaches exist, giv
## Vibe Coding: The Entry Point
[IMAGE: comic. Young developer with coffee sitting at workstation. Then coffee spills on keyboard. Developer puts on headset with mic and says: "Ok, I'm a vibe coder now". Style: Cartoon/illustration, warm colors, relatable developer humor]
![Comic: Developer shows Karpathy's vibe coding tweet, colleague says now he can do this officially](https://cdn.banatie.app/blog/henry-devto/img/c4c24f43-d0ac-45d2-84d0-6cb0624a8957)
**What it is:**
- Popularized by Andrej Karpathy (February 2025)
@ -57,7 +57,7 @@ So what are these methods?
## Spec-Driven Development: Structure First
[IMAGE: comic. Two panels. First young developer leans back in chair, bragging: "Look, thanks to my prompt, AI generated perfect code for the new feature in 15 minutes." Second young developer: "You spent 6 hours writing that prompt"]
![Comic: Developer brags AI generated code in 15 minutes, colleague points out he spent 6 hours writing the prompt](https://cdn.banatie.app/blog/henry-devto/img/79c4c6fd-129a-499f-be04-f503eff018b5)
**Credentials:**
- Formalized by GitHub Engineering Team ([GitHub Spec Kit](https://github.com/github/spec-kit), September 2025)
@ -90,7 +90,7 @@ Use Claude Desktop for spec development: give it Filesystem MCP for code access,
## Agentic Coding: High Autonomy
[IMAGE: comic. Woman asks a builder: "Are you sure your autonomous androids are suitable for building our playground?" She shows him a diagram with a swing and carousel. Builder in hard hat replies: "Oh yes, I gave them clear instructions and 24 hours of autonomy. Let's see how they did." Final panel: woman and builder stand dumbfounded, mouths open, looking at a mega-futuristic entertainment center]
![Comic: Builder gives autonomous androids task to build playground, they overengineer into theme park](https://cdn.banatie.app/blog/henry-devto/img/031320e3-9252-4c6a-9c98-e08d7ef40855)
**Credentials:**
- Academic research: [arXiv 2508.11126](https://arxiv.org/abs/2508.11126) "AI Agentic Programming: A Survey" (UC San Diego, Carnegie Mellon, August 2025), [arXiv 2512.14012](https://arxiv.org/abs/2512.14012) "Professional Software Developers Don't Vibe, They Control" (University of Michigan, December 2025)
@ -130,7 +130,7 @@ Try to set up your environment so the agent can't do anything that git reset cou
## AI Pair Programming: Working Together
[IMAGE: comic. Programmer with headphones at computer. AI suggestions float out of headphones as bubbles: "maybe use map?", "add null check", "async would be better here". Programmer looks at them with irritation. Caption: "When AI knows better, but you want to do it your way"]
![Comic: Developer tries to type simple code while AI bombards with irrelevant suggestions](https://cdn.banatie.app/blog/henry-devto/img/8bea3b16-f764-4212-8c09-918b87668884)
**Credentials:**
- GitHub official positioning: "Your AI pair programmer" (Copilot marketing since 2021)
@ -213,7 +213,7 @@ Write tests BEFORE implementation (classic TDD). AI generates code to pass tests
Red → Green → Refactor cycle, but AI handles implementation. Tests catch AI mistakes automatically. Tests provide verification without human review of every line.
[IMAGE: comic. First developer: "What are you doing now?" Second: "I'm developing universal tests to verify unit test writing by our coding agents." First: "Are you doing this yourself?" Second: "No, I gave the task to an autonomous AI agent"]
![Comic: Developer writes tests to verify AI agent code using another AI agent](https://cdn.banatie.app/blog/henry-devto/img/94559d7c-06ab-4e5f-860a-87419906f3b5)
**Tests as specification:**