In early 2025, Andrej Karpathy posted a description of his new coding workflow: no rigid architecture planning, no extensive debugging sessions — just vibes, LLM assistance, and shipping. He called it "vibe coding." The internet, specifically the developer corner of it, immediately split into two camps: people who thought it was brilliant and people who thought it was a crime against computer science. Both camps immediately started doing it.
The vibe coding shirt is for both camps. Because at the end of the day, everyone who codes has had a session where the architecture was "trust," the tests were "we'll see," and the deploy was on a prayer. That's vibe coding. The shirt just makes it official.
Key Takeaways
- Vibe coding was coined by Andrej Karpathy in 2025 to describe AI-assisted, intuition-driven development
- It became a developer identity marker almost immediately — a shorthand for a style of working, not just a technique
- According to the 2025 GitHub Octoverse report, AI-assisted coding now accounts for over 40% of code written on the platform
- The vibe coding shirt signals membership in a specific moment in developer culture — post-LLM, flow-state focused, ships-first
- Soft, dark, minimal — the aesthetic matches the workflow
What Is Vibe Coding?
The 2025 developer workflow
Vibe coding is roughly: use AI heavily, iterate fast, don't overthink the architecture, trust the flow. It's less about ignoring best practices and more about a different relationship with the development process — one where the LLM is a collaborator and the developer is steering by intuition and outcome rather than strict methodology.
According to the 2025 GitHub Octoverse report, AI-assisted coding now accounts for over 40% of code written on GitHub. Vibe coding is the cultural name for what that feels like at 11pm when you've shipped three features in two hours and none of them have broken production yet.
Why it became an identity marker
It became an identity marker because it captured something real: there's a generation of developers who learned to code with AI assistance from day one, and their workflow looks genuinely different from the engineer who wrote bare-metal C in 1998. The vibe coding shirt is a flag for that generation — and for everyone who's been in the industry long enough to recognise the irony of having a name for what they've always done on Fridays when the deadline is Monday.
The Vibe Coding Shirt
What it signals
It signals: I ship. I iterate. I have opinions about AI-assisted development but I'm not going to make them your problem right now because I'm in flow state and the feature is almost done.
Also: I know what vibe coding is, which means I've been paying attention to the culture, which means I'm probably fun to pair with.
The Testing In Prod Neon Shirt is the natural sibling — same energy, different specific sin.
Who wears it
Vibe coders, obviously. But also: engineers who find the whole discourse funny. People who want to start a conversation at a hackathon. Developers who are deeply serious about their craft and enjoy wearing a shirt that suggests otherwise.
Vibe Coding Culture
From Andrej Karpathy tweet to developer identity
The term went from a single post to an industry debate in about 72 hours. Think pieces appeared. Counter-think-pieces appeared. Someone built a "vibe coding" mode into their IDE. The term is now in common use in developer Slack channels, conference talks, and apparently, t-shirts.
That's how developer culture works: an observation becomes a meme becomes an identity marker becomes merchandise. The speed of that cycle is itself a vibe coding outcome.
The debate (and why it doesn't matter)
Some engineers think vibe coding produces unmaintainable code. Some think it's the future of software development. Both are probably right in different contexts. The shirt doesn't take a position — it just acknowledges that the thing exists and that you know about it, which is enough.
Frequently Asked Questions
What does vibe coding mean?
Vibe coding refers to a development style, popularised by Andrej Karpathy in 2025, that emphasises AI-assisted iteration, intuition-driven decisions, and shipping over strict methodology. It's less a formal practice and more a cultural shorthand for a particular relationship with the development process — fast, flow-state, LLM-assisted.
Is vibe coding a legitimate development approach?
That depends on who you ask and what you're building. For rapid prototyping, personal projects, and early-stage products, it's highly effective. For critical infrastructure, the vibes probably need some unit tests. The shirt doesn't have opinions on this.
What does the vibe coding shirt look like?
Clean typography on a dark background — the Code Culture design language. The phrase is prominent, the design is minimal, the quality is not. It's a shirt you'd wear to a hackathon, a conference, or daily as a developer who wants to signal cultural awareness without a lengthy explanation.
Who is the vibe coding shirt for?
Any developer who knows what vibe coding means — which is most developers who've been paying attention to the industry since 2025. It's also a good gift for engineers who are clearly vibing but haven't officially named their methodology yet.
What material is the vibe coding shirt made from?
100% combed ring-spun cotton, soft and durable for daily wear. The print is high-quality and survives repeated washing. Available in XS through 3XL.
Written by Emcy — data professional, software engineer, and Code Culture founder. Emcy has worked in data engineering for 8+ years, attended dozens of tech conferences across Europe, and started Code Culture because developer apparel deserved better than novelty gift shop tier. Based in Utrecht, Netherlands.