When Lobste.rs introduced the “vibe coding” tag to mean any post relating to LLMs part of <a href=“https://lobste.rs/s/lkngrz/new_tag_vibecoding” rel=“ugc”>the justification for that decision</a> was this, where the industry is settling on link targeted the O’Reilly “Vibe Coding: The Future of Programming” page (<a href=“https://web.archive.org/web/20250417003503/https://www.oreilly.com/library/view/vibe-coding-the/9798341634749/” rel=“ugc”>Internet Archive here</a>). <blockquote> We kicked around a bunch of ideas, but <a href=“https://en.wikipedia.org/wiki/Vibe_coding” rel=“ugc”>vibe coding</a> seems to be the term the <a href=“https://www.oreilly.com/library/view/vibe-coding-the/9798341634749/” rel=“ugc”>industry is settling on</a>. </blockquote> That O’Reilly book has been renamed! It’s now called “Beyond Vibe Coding: From Coder to AI-Era Developer”, acknowledging that Vibe Coding is the act of prompting an LLM to produce software without caring about or reviewing the code. Here’s more from the author’s <a href=“https://beyond.addy.ie/” rel=“ugc”>site about the book</a>: <blockquote> Vibe coding was never meant to describe all AI-assisted coding. It’s a specific approach where you don’t read the AI’s code before running it. There’s much more to consider beyond the prototype for production systems. […] AI-assisted engineering is a more structured approach that combines the creativity of vibe coding with the rigor of traditional engineering practices. It involves specs, rigor and emphasizes collaboration between human developers and AI tools, ensuring that the final product is not only functional but also maintainable and secure. </blockquote> Now that the O’Reilly have accepted the <a href=“https://simonwillison.net/2025/Mar/19/vibe-coding/” rel=“ugc”>original Karpathy definition</a> of “vibe coding”, maybe Lobste.rs could too? I think the obvious better name for the tag at this point, given the way it has been used for the past four months, is simply llms.