1 year of vibe coding — retrospective

X / TwitterApr 19, 2026

Original excerpt

A lot of people quote tweeted this as 1 year anniversary of vibe coding. Some retrospective - I've had a Twitter account for 17 years now (omg) and I still can't predict my tweet engagement basically at all. This was a shower of thoughts throwaway tweet that I just fired off without thinking but somehow it minted a fitting name at the right moment for something that a lot of people were feeling at the same time, so here we are: vibe coding is now mentioned on my Wikipedia as a major memetic "contribution" and even its article is longer. lol The one thing I'd add is that at the time, LLM capability was low enough that you'd mostly use vibe coding for fun throwaway projects, demos and…

Frequently asked questions

What is "1 year of vibe coding — retrospective" about?

This article by Vibe Coding is part of the Vibe Coding reading list on Burn 451, covering post-code ai era.

Who wrote "1 year of vibe coding — retrospective"?

This piece is part of the Vibe Coding vault on Burn 451, covering post-code ai era. The original author is attributed at the source link.

How can I read more content from Vibe Coding?

The complete Vibe Coding reading list is available at burn451.cloud/vault/vibe-coding. Each article includes an AI-generated summary so you can decide what to read in seconds. Connect the Burn 451 MCP server to Claude or Cursor to query all Vibe Coding articles as live AI context.

Can I use "1 year of vibe coding — retrospective" with Claude or Cursor?

Yes. Install the burn-mcp-server npm package and connect it to Claude Desktop, Claude Code, or Cursor. Once connected, your AI can search and reference this article and the full Vibe Coding vault in real time — no manual copy-paste required.

19 more articles in this vault.

Import the full Vibe Coding vault to Burn 451 and build your own knowledge base.

Content attributed to the original author. Burn 451 curates publicly available writing as a reading index. For removal requests, contact @hawking520.