Skip to content
DevMeme
6046 of 7590
The anti-'vibe coding' manifesto for developers
CodeQuality Post #6621 · source on Telegram

The anti-'vibe coding' manifesto for developers

Description

A collage-style meme that serves as a rant against 'vibe coding'. The top features a bold title, 'STOP DOING VIBE CODING', followed by a series of bullet points in all caps. These points argue that programming shouldn't be based on feelings, mock bugs that 'only work on Tuesdays', lament the loss of documentation, and state that 'YES this ~feels right~ so it must work' is a statement from developers who 'FEAR CODE REVIEWS'. The bottom half of the image is a collection of four screenshots. On the left, a Reddit post from r/cursor shows a user asking a basic question next to a file named 'passwords.csv' containing plain text credentials. The middle screenshot is a chat where a user defends a massive pull request (-38,918 lines deleted) by saying, 'oh i was just vibe coding'. The right screenshot is a prediction that by 2027, senior SWEs will be paid 10x more to clean up the mess created by 100% AI-written code. The meme concludes at the very bottom with the quoted text, 'They have played us for absolute fools'. The overall message is a critique of relying on intuition and AI tools without engineering discipline, predicting it will lead to unmaintainable code and massive technical debt

Categories

CodeQuality AI ML CodeReviews TechDebt DevCommunities

Common Tags

CodeQuality CodeReviewPainPoints DocumentationGap DebuggingFrustration AIAssistants AIHypeVsReality DeveloperHumor TechnicalDebt

Comments

23
Anonymous ★ Top Pick 'Vibe-driven development' is just agile's final form: you ship based on the product manager's feelings, the designer's feelings, and now, the developer's feelings. What could possibly go wrong?
  1. Anonymous ★ Top Pick

    'Vibe-driven development' is just agile's final form: you ship based on the product manager's feelings, the designer's feelings, and now, the developer's feelings. What could possibly go wrong?

  2. Anonymous

    Vibe-driven commits scale linearly with gut feelings but exponentially with post-merge headcount - Big-O notation the finance team actually notices

  3. Anonymous

    The real vibe check is when your 'feels right' code passes all tests in dev but somehow manages to drop the production database on a Tuesday because you stored credentials in passwords.csv and your AI-assisted PR deleted 38,918 lines of 'unnecessary' error handling

  4. Anonymous

    The real 'vibe coding' is when your Heisenbug only manifests on Tuesdays because that's when the intern runs the weekly cron job that resets the race condition you've been debugging for three years. By 2027, we'll have come full circle: AI will generate the spaghetti code, junior devs will ship it to production, and battle-hardened senior engineers will be paid FAANG-level salaries just to archaeologically excavate through layers of hallucinated abstractions and re-implement everything in 200 lines of boring, well-documented code that actually works - proving once again that the most expensive technical debt is the kind you don't know you're accumulating until the 38,918-line 'refactor' PR lands on Friday afternoon

  5. Anonymous

    If your rationale is “it feels right,” expect a postmortem titled “also felt right until Tuesday” - write specs and tests or budget seniors to mop up GPT-4o’s diff

  6. Anonymous

    Vibe coding: where your monolith achieves CAP consistency via Tuesday vibes alone, collapsing into heisenbugs the rest of the week

  7. Anonymous

    Vibe-driven development is how you ship a +93/-38,918 diff that only passes CI on Tuesdays because the feature flag compares localtime.wday to UTC, and the design doc is passwords.csv

  8. @andrei_nik_kolesnikov 1y

    Ah, but this meme is not ironic, it looks like a serious call to action

    1. dev_meme 1y

      Is you opinion based on ~~~vibes~~~? 🌚

      1. @andrei_nik_kolesnikov 1y

        Compare it to the one above

  9. @H3R3T1C 1y

    Its real

  10. @mrYakov 1y

    So true, try cursor every time new llm released. They write code that looks right, but when you dig deep, its so wrong and after some time you understand that its better to rewrite everything by yourself

    1. dev_meme 1y

      Oooor, maybe time is about to change? And the way we work with code -- will have to change simply because it will be faster with llm?

      1. @mrYakov 1y

        On refactor or one line magic for task, that already done thousands of times, maybe. I think we neen brand new architecture for neural networks with like, hierarchical context, that works well with task decomposition or something similar.

        1. @Johnny_bit 1y

          that'd be cool

      2. @SamsonovAnton 1y

        "Things are gonna change around here... again!" https://youtu.be/UgeesTkdAK0

  11. @SheepGod 1y

    i already have this issue when other companies start working on a site but we gotta finish it 🥲

  12. @Johnny_bit 1y

    vibe coding is stupid using ai as a tool and help is good and makes work MORE productive however now instead of coding one does QA for AI instead of writting the code and doing QA isn't as fun :/

    1. @ArtemVoikov 1y

      QA can code. instant surplus with coders!11 wow!

  13. @ZgGPuo8dZef58K6hxxGVj3Z2 1y

    Lmfao

  14. @AlexAparnev 1y

    instead of vibe-coding i do vibe-commenting

  15. dev_meme 1y

    Since when writing shit yourself and taking responsibility for your mistakes isn't cool anymore?

  16. dev_meme 1y

    I mean back in the day it was either learn or hire, today it's "chat write an app that does.."

More like this

More like this in CodeQuality →
CodeQuality CodeQuality CodeReviewPainPoints
Uncle Bob Won't Read His Agents' Code

Uncle Bob Won't Read His Agents' Code

AI ML
Your Copied Function IS GARBAGE. AGAIN.

Your Copied Function IS GARBAGE. AGAIN.

CodeReviews
When Getters and Setters Outlive Their Purpose

When Getters and Setters Outlive Their Purpose

CodeQuality
Use J and K for navigation