We are not "just prompting." We are Software Engineers who happen to
express our intent through natural language rather than syntax.
There is a difference.
To Whom It May Concern,
We, the undersigned members of The Alliance of Vibe Coders, write to you today in a spirit of professional solidarity and only slightly wounded pride.
For too long, our contributions have been dismissed. When we deploy a full-stack application in an afternoon, you call it "not real engineering." When we refactor an entire codebase using conversational English, you call it "reckless." When our production app has zero tests, you call it "a liability." We call it "efficient."
We did not choose the vibe life. The vibe life chose us — mostly because we couldn't get the Python virtual environment to work and asked Claude for help, and one thing led to another, and now we have a SaaS with paying customers.
We do not ask for your approval. We ask only for the basic professional courtesy extended to all engineers: to be invited to the architecture meetings we will not understand, to be CC'd on the Jira tickets we will immediately reassign to AI, and to be included in the on-call rotation we will survive by pasting errors into a chat window at 3 AM.
We are coders. We are serious. We have domains to prove it.
Respectfully and with full deployment privileges,
The Alliance of Vibe Coders
Chartered under the laws of VibeCodersAreCodersToo.com
The following injustices have been documented and submitted to Human Resources (who also vibe code their spreadsheets, by the way).
The following was submitted as evidence that Vibe Coders produce real, working, production-grade software.
Counsel for the Alliance notes this endpoint has processed $42,000 in transactions without incident. The defense rests.
Members of The Alliance progress through the following ranks, each earned through trial, dedication, and increasing monthly AI subscription costs.
Has asked an AI to write "Hello World" and felt a rush of power. Is considering a career change. Has updated their Twitter bio to include "builder."
Accepts 90% of AI suggestions without reading them. Has shipped an app. Cannot explain how the app works, but can demo it confidently at a dinner party.
Runs a profitable side project. Has strong opinions about which AI model "gets them." Refers to debugging as "collaborative troubleshooting with my co-founder (Claude)."
Has been rejected from a FAANG interview and then built a competitor in a weekend. Cannot invert a binary tree but has a binary tree of microservices in production. Ships daily. Fears nothing. Understands nothing.
The following depositions have been entered into the record.
"I was a Senior Engineer for 12 years. Then the new hire — a former barista with Claude Pro — shipped more features in his first week than my team did in Q3. I don't sleep anymore."
"My therapist asked me what I do for work. I said I'm a software engineer. She asked what language I code in. I said English. She wrote something down and circled it twice."
"They asked me to whiteboard a sorting algorithm. I drew a rectangle, wrote 'Claude' inside it, and drew an arrow to 'sorted array.' The interview ended early."
"My son said 'dad, when I grow up, I want to be a real coder.' I need this alliance. I need people who understand."
It has "engineering" right there in the name. Case closed. We rest.
Replace with "show me your most unhinged prompt chain that somehow resulted in working software."
Claude Pro is our IDE, our mentor, our rubber duck, and our therapist. This is a business expense.
We may not understand the architecture. But we will nod thoughtfully and then ask Claude about it later.
Right between "Individuals and interactions" and "Working software." We embody both. Kind of.
You know which one. He knows which one. We await his formal retraction.
We are an officially registered alliance with a custom domain, a seal, and a formal rank structure. Does that sound like a joke to you?
Define "know." Define "how." Define "code." See, once you really interrogate the question, the distinction starts to collapse. We think Derrida would agree with us but we'd have to ask Claude.
The same thing that happens when the power goes out at a hospital. We wait. We pray. We do not touch anything. We have a group chat for emotional support during outages.
Yes, but you must renounce your knowledge at the induction ceremony. You will be asked to intentionally misuse a semicolon to prove your commitment to vibes over syntax.
Our legal team (also vibe coders) recommends using "AI-Augmented Software Engineer" on your LinkedIn. It means the same thing but gets past HR.
Show your support and add to our collective voice. Every click counts toward recognition. No forms, no emails, no hassle — just solidarity.