<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/vibe-coding-is-ruining-the-vibe-wstkf2fdb" -->

---
title: Vibe coding is ruining the vibe | daily.dev
description: A senior software engineer reflects personally on how AI-assisted 'vibe coding' has changed the craft of programming, proposing a six-level scale from using AI...
canonical: https://daily.dev/posts/vibe-coding-is-ruining-the-vibe-wstkf2fdb
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Vibe coding is ruining the vibe | daily.dev
og:description: A senior software engineer reflects personally on how AI-assisted 'vibe coding' has changed the craft of programming, proposing a six-level scale from using AI...
og:url: https://daily.dev/posts/vibe-coding-is-ruining-the-vibe-wstkf2fdb
og:image: https://api.daily.dev/og/posts/WStkf2fdB.png
og:image:alt: Vibe coding is ruining the vibe
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Vibe coding is ruining the vibe

**[public class Name](https://daily.dev/sources/bysqapzoninhiaruymkd7)** · [@makotolord](https://daily.dev/makotolord) · 7 min read · 1 upvotes · 0 comments

## Summary

A senior software engineer reflects personally on how AI-assisted 'vibe coding' has changed the craft of programming, proposing a six-level scale from using AI as a smarter search engine up to blindly accepting all AI output without critical thought. The piece argues responsible use matters more than the tool itself, and warns that over-reliance erodes learning and the intrinsic joy of coding. It closes with five practical habits to counteract skill atrophy: deliberately coding without AI on small projects, revisiting old technologies, re-doing poorly understood AI-generated work, practicing critical thinking, and using LLMs only to generate practice exercises.

## Content

Yeah yeah I know, another article about GenAi, feel free to skip this one...or don't. I seriously don't mind, this is just me offering my own opinion and maybe I'll get a few people agreeing or disagreeing with me along the way.

If you're still reading this, it means you want to hear my unsanitsed thoughts. Great.

Vibe coding is an interesting premise. Every coder has at least tried it once, don't lie... you have tried it at least once. You may think you're above it (maybe you are) but you aren't always going to be writing the boilerplate by hand, are you?

It has helped great programmers become greater, good programmers become mediocre and mediocre programmers become the equivalent of a client. Companies want you to vibe it along the way but responsibly of course. Not saying allow all on claude code, understanding the specs and adapting along the way. Of course not everyone does this, a lot of people in workplaces use co pilot to refine their responses, hit that allow all, leave in their comments with the little quirky emojis, without explaining what they originally wrote.

Vibe coding, although controversial, is just a change to allow us to get our work done quicker.Programming whether it be a hobby or job, has changed along the way. Gone are the days of memory management, sooner or later we had garbage collectors and now we have prompts....then all these wacky ways of automating the prompts.

AI doomers and AI...(what's the opposite of "Doomer"..."Boomer", "Loomer"...ah whatever)

They both either idolise or despise Generative AI without being grounded at all in their facts and opinions. AI tools can be used to find new cures and advanced medicine and health-care. They can help your 77 year old grandad create something that makes his life easier and may not have been so keen on starting in the first place. However, it can also be used to create outrageous and illegal deepfakes, lie to people using it or even lead to that poor Grandpa making uninformed decisions. At the end of the day, it's how you use it. Humans need to be responsible when using AI tools and that's on so many different levels.

Here's what I mean:

Level one: Using AI to help you learn how to do things, it's a better Google search and you can ask follow up questions or ask it to explain a concept you'd better understand if it referenced something you already understood.

Level Two: Using it to do things you already know how to do, you do some of the stuff as well but it clears up the boring stuff.

Level three: You architect the design and structure, you know how it all should come together but you get Ai to do most of it for you.

Level four: You get it to do things you don't know how to do but you still fact check.

Level five: You do level three but no fact checking.

Level six: You no longer think critically, you just get it to do everything.

![Screenshot_20260906_010248_Claude.jpg](https://media.daily.dev/image/upload/s--tZhK884k--/f_auto/v1788653057/ugc/content_b6e209bc-8f5d-4463-ace1-66122edd7da4?_a=BAMAMicg0)

A big difference between vibe coders and vibing in other fields is that artists and writers are genuinely not looking at the end goal like we do. Art takes time and precision, it can be enjoyable. Writing can be therapeutic, especially opinionate pieces like this...not exactly an opinion if you're asking Gemini what to write. Coders mostly want to see a finished product whether that's a compression algorithm for their application or simply centering a div. If I can remove the boring stuff, then what's the big deal?

The issue is, it can stop you from learning when you rely on it too much.  Think about a time before vibe coding. Stackoverflow. Back then, you may have been a copy and paster BUT at least you had to read the problem. Sometimes interact with the code, if it was doing something slightly different from what you desired. Now you either paste your code to an AI of your choice or give your repo to codex or claude code and tap allow or enter every 5 minutes.

If you wanted to design something new or learn a new framework, you'd read the docs, learn it, fail and succeed. Now you say "I want to create this" and Chat or Deepseek will say "Okay sounds good, want help creating this?" and you just go with it. It's okay, everyone does it sometimes. I'm guilty of it. I needed help creating a minecraft mod today and even though I architected things and designed the mobs, I still got claude code to modify the code for me. I know Java, I could've done it myself but I wanted it done in an hour. Earlier, I mentioned how a lot of programmers like to see an end result with their code but it is genuinely grattifying to code on the other hand as well. A lot of programmers say coding used to be fun, before the introduction of LLM's. I see it too, honestly. I remember when I was very junior and I was learning Typescript with React, and even though every day I made very little progress, just creating a UI component was enough for me to feel giddy but now it's like what's the point if I just got claude code to make everything?

Don't get me wrong, it's great to have things done so quickly but it does also remove the fun sometimes. I'm now a senior software engineer and as one, I have been using new methods to ensure I stay on top of things and I'd like to share 5 of those here as they may help someone who reads this.

5) Pick a topic to non vibe code:

Pick a small topic, maybe it's just build a Java Web app or try GraphQL. Use only the docs and try to make it. It doesn't have to be spectacular just good enough to master the basics. This will help ensure you are able to remember how to do core things.

4) Go back and re-learn topics

This is a no brainer but always go back to old technologies or tools you have used and try to just practice it as much as you can.

3) Try to re-learn anything you did level 4-6 on. If you deployed an app to EKS but your understanding of the yaml file was scarcely limited, go back and try to understand what you did and try and even just do it yourself. This may take longer..especially if you did a lot but it's worth it in order to retain this information and you'll be a stronger programmer because of it.

2) Practice critical thinking and innovation.

Think with your brain with no other influencers about what you know and the solutions you want to come up with. For example, if there's a problem at work, think critically of an approach that could help solve that problem quite easily. Think of the tools, stack and what sort of support that solution should need.

1) Use an LLM of your choice to give you problems or exercises to get through

Yes, I know I said no vibing but you can get AI to create you questions, and those questions could be trivial or be coding exercises you can attempt or questions that test your knowledge about a certain area.

Thanks for reading!

## Similar posts on daily.dev

- [From Programmer to Prompt Monkey: The Trap of Vibe Coding](https://daily.dev/posts/from-programmer-to-prompt-monkey-the-trap-of-vibe-coding-nxul05hrf) · Medium · 3 upvotes · 0 comments
- [Breaking the Spell of Vibe Coding – fast.ai](https://daily.dev/posts/breaking-the-spell-of-vibe-coding-fast-ai-fpz532s1x) · fast.ai · 0 upvotes · 0 comments
- [Reports of code's death are greatly exaggerated](https://daily.dev/posts/reports-of-code-s-death-are-greatly-exaggerated-3336mspgf) · Hacker News · 14 upvotes · 2 comments

---

Tags: [#github](https://daily.dev/tags/github), [#ai-coding](https://daily.dev/tags/ai-coding), [#claude-code](https://daily.dev/tags/claude-code), [#vibe-coding](https://daily.dev/tags/vibe-coding)

[View this post on daily.dev](https://daily.dev/posts/vibe-coding-is-ruining-the-vibe-wstkf2fdb)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/vibe-coding-is-ruining-the-vibe-wstkf2fdb","headline":"Vibe coding is ruining the vibe","text":"A senior software engineer reflects personally on how AI-assisted 'vibe coding' has changed the craft of programming, proposing a six-level scale from using AI as a smarter search engine up to blindly accepting all AI output without critical thought. The piece argues responsible use matters more than the tool itself, and warns that over-reliance erodes learning and the intrinsic joy of coding. It closes with five practical habits to counteract skill atrophy: deliberately coding without AI on small projects, revisiting old technologies, re-doing poorly understood AI-generated work, practicing critical thinking, and using LLMs only to generate practice exercises.","url":"https://daily.dev/posts/vibe-coding-is-ruining-the-vibe-wstkf2fdb","datePublished":"2026-09-06T00:41:32.046Z","dateModified":"2026-09-13T21:30:53.817Z","author":{"@type":"Person","name":"public class Name","url":"https://daily.dev/makotolord","image":"https://media.daily.dev/image/upload/s--YQz_8Z2N--/f_auto/v1752520309/avatars/avatar_BySqApZoninHIarUYmkD7?_a=BAMClqZW0","description":"Breaking news: Nerd looks at other nerd posts ","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":210}},"interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/sources/bysqapzoninhiaruymkd7","name":"public class Name"}}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"public class Name","item":"https://daily.dev/sources/bysqapzoninhiaruymkd7"},{"@type":"ListItem","position":3,"name":"Vibe coding is ruining the vibe"}]}
```

