Here is one of the dumbest things about vibe coding that I don't see a lot of people talking about

Imagine you're an open source maintainer and someone opens up a pull request against your repository that they vibe coded.  They may or may not tell you they vibe coded it; it doesn't really matter… 🧵

Lobsters is a community-driven platform for sharing and discussing links to articles, tutorials, and projects related to technology and programming. Readers can learn about a wide range of topics, from software development and system administration to cybersecurity and artificial intelligence. With user submissions, comments, and voting, Lobsters provides a platform for collaborative learning and knowledge sharing among technology enthusiasts.

Lobsters

AI-assisted coding ("vibe coding") creates a problematic dynamic in open source contributions where contributors who don't understand their own code feed reviewer comments back into AI models, effectively turning maintainers into unwitting prompt engineers. The core issue is that using AI to write code erodes codebase familiarity, making users progressively less capable of meaningfully driving the model or understanding their own contributions. This creates a cycle where someone must still do the hard work of understanding the code, but vibe coding trades that understanding for short-term productivity gains at the expense of long-term project health.

Post by @fullmoon.id — Bluesky