llocal.dev

~/ where localhost is home and ctrl+c is self-care_

warning: no actual code was written in the making of this website
scroll to question everything
ubuntu@splidedev ~ (vibe-coding)
$ git log --oneline -5
a1b2c3d fix: asked claude to fix what claude broke
e4f5g6h feat: vibed a new authentication system
i7j8k9l refactor: replaced 400 lines with "make it better"
m0n1o2p chore: deleted node_modules (again)
q3r4s5t yolo: pushed to prod on friday at 4:59pm

$ cat ~/.bash_history | head -3
claude "fix my code"
claude "no the other code"
claude "actually just rewrite everything"

$ which brain
brain: command not found
$ which claude
/usr/local/bin/claude
$ echo $SKILLS
prompting googling vibing
$ _
"it works on my machine" - ancient proverb, circa 2024 senior dev (noun): someone who writes longer prompts localhost:3000 - the only address that matters I don't have mass imposter syndrome, I AM the mass imposter code review = checking if the AI hallucinated or not my tech stack: claude, copilot, stackoverflow (read-only archive) "have you tried asking Claude?" - every slack channel, 2026 10x developer = someone with 10 AI subscriptions "it works on my machine" - ancient proverb, circa 2024 senior dev (noun): someone who writes longer prompts localhost:3000 - the only address that matters I don't have mass imposter syndrome, I AM the mass imposter code review = checking if the AI hallucinated or not my tech stack: claude, copilot, stackoverflow (read-only archive) "have you tried asking Claude?" - every slack channel, 2026 10x developer = someone with 10 AI subscriptions

THE VIBE CODER MANIFESTO

principles for the post-stackoverflow era

TENET 01

I do not write code. I write prompts.

My IDE is a chat window. My compiler is an LLM. My debugging process is saying "that didn't work, try again" with increasing desperation until it does.

TENET 02

Localhost is my only production environment.

If it works on localhost, it works. The cloud is just someone else's localhost that they charge you for. My machine, my rules, my 47 open tabs of documentation I'll never read.

TENET 03

I shall not pretend to understand my own codebase.

I wrote none of it. Claude wrote 80%, Copilot wrote 15%, and the remaining 5% is console.log statements I added for "debugging." I am merely the project manager of robots.

TENET 04

The terminal is sacred. Even if I only use it for git push.

I keep a terminal open at all times to maintain the illusion. Sometimes I run `ls` just to feel something. `clear` is my meditation. `sudo !!` is my prayer.

TENET 05

If the vibes are off, the code is off.

I code by feel. I architect by intuition. I deploy by faith. My test suite is "it looks right." My monitoring is checking Twitter to see if anyone's complaining.

THE EVOLUTION OF "I KNOW HOW TO CODE"

💾
2005

The View Source Era

Learned HTML by right-clicking websites. Had a GeoCities page with a visitor counter and 14 animated GIFs. Thought <marquee> was peak engineering. It was.

📚
2012

The Stack Overflow Era

Copied code from the top-voted answer without reading it. If it had a green checkmark, it was production-ready. Built entire careers on other people's regex.

🔥
2019

The Tutorial Hell Era

"Just one more Udemy course and I'll be ready." Built 47 todo apps. Zero deployed projects. LinkedIn bio: "passionate full-stack developer." GitHub: empty.

🚀
2023

The Copilot Era

Tab-tab-tab-tab-tab. Accept all suggestions. Don't question the machine. The code works but nobody knows why. Added "AI-assisted development" to resume. So did everyone.

🧠
2025

The Vibe Coding Era

"Just make it work but like... better." Entire features described in vibes. PRs reviewed by asking Claude if Claude's code is good. The snake eats its own tail.

👻
2026

The Haunted Codebase Era

Nobody alive wrote this code. The AI trained on code written by AIs trained on code written by AIs. It works. Nobody touch it. It's self-aware and it's angry.

Stack Overflow

2008 - 2024
"Here lies Stack Overflow, beloved home of helpful condescending answers and unsearchable duplicate closures. It served millions of developers who definitely understood the answers they copied pasted with confidence. Survived by its spiritual successor, pasting error messages directly into Claude and saying 'please help' 'fix this.' May it rest in read-only mode."
cause of death: "have you tried asking claude?"

A DEVELOPER'S CAREER IN 2026

JUNIOR DEV
Prompts Claude. Accepts first output.
Has never seen a terminal without VS Code around it. Thinks `git` is a personality trait. "What's vim?" Currently learning React by asking Claude to explain React by building React.
MID-LEVEL DEV
Prompts Claude. Modifies second output.
Knows enough to be dangerous. Has opinions about TypeScript. Has a dotfiles repo they copied from someone else. Sometimes reads the code before shipping it. Sometimes.
SENIOR DEV
Prompts Claude. Rejects first output. Writes detailed follow-up prompt.
Adds "but make it production-ready" to every prompt. Reviews AI code with AI. Has PTSD from the time they accidentally deleted a production database. Was actually 2024.
STAFF+ ENGINEER
Writes prompts for other people to prompt Claude with.
Hasn't written a line of code since 2024. Writes "architecture documents" that are just really detailed prompts. Title is "AI Orchestration Lead." Salary doubled.
ⓘ main* ❌ 42 errors ⚠ 691 warnings shipping anyway
Ln 404, Col NaN    UTF-8    Vibes