A Vibe Coder
Posts
A Vibe Coder's Manifesto

A Vibe Coder's Manifesto

Code coded.

Edgar San Martin
September 04, 2025 • Estimated Reading Time: 3 minutes

From Edgar,

Welcome to A Vibe Coder, my newsletter where I upload my thoughts on current tech trends, experiements, and vibe coding best practices.

Shilling Myself

Unveil

AI Game Engine to build your dream 2D and 3D game. Pre-YC Funded (;

Pre-Order: Discounted month of AI usage. Base engine will be free, but your support helps.

Tini La

A better Linktr.ee. Advance anayltics, easy (GDRP-compliant) email capture.

20% Off 1st Year: Use promo code LALALA at checkout when you sub to our Pro Yearly plan.

Manifesto

Vibe coding is not the absence of structure. It’s engineering in motion. People sometimes mistake it for chaos. They throw code together, or worse, let AI do it all. But that isn’t vibe coding. That’s laziness dressed up as speed.

Without real knowledge, you won’t get far. You can’t bend a tool you don’t understand. AI can suggest things, but you can’t shortcut the shortcut. If you don’t know why the code works, you won’t know when it doesn’t.

The process usually starts with a spark. A mechanic. A system. A “what if.” That spark is important, but it’s only a beginning. To keep it alive, you need to shape it. Research with an LLM. Dig through forums. Explore the real world. The best ideas come when vision meets reality.

The goal is to move fast, but not aimlessly. Sloppy code that never grows up is a dead end. Vibe coding isn’t about hacks that fall apart the first time someone leans on them. It’s about writing code quickly, with enough structure to support the next step. The first draft doesn’t have to be perfect. But it has to be an honest effort.

In short:

Learn deeply.
Use AI, but don’t outsource your judgment.
Build from vision, feed that with knowledge.
Treat vibe coding as engineering.

The world rewards people who can turn sparks into systems. That’s what vibe coding is for. It collapses the distance between an idea and something real. And the faster you collapse that distance, the more you can learn, the more you can build, and the more likely you are to make something that lasts.

Thank Y’all

I’ve taught myself to code. Been an engineer for 8 years. Went all in on vibe coding this past year (after resistance) and it’s now a major part of my workflows. I hope my experiences will help you be a better vibe coder.