Yesterday, I made the "Bull Case" for WordPress: Use it as a battle-tested foundation so you don't have to reinvent the bricks. But there’s a new trap appearing for architects building on these foundations: Vibe Coding. 🧵
"Vibe Coding" is when you use AI to spin up a beautiful UI in seconds. It looks great. It feels right. It has the "vibe." But a "vibe" isn't a system. And when you prioritize the vibe over the design system, you’re building technical debt at 10x speed.
The temptation is real: Why spend hours on tokens, documentation, and reusable components when AI can just "give me a hero section that looks like Apple"? Because AI-generated interfaces are often "one-offs." They look consistent until you try to scale.
In my latest post, I break down why the "Vibe Coding Trap" is the hidden tax of AI-accelerated development. If we skip the "boring" systemic work, we lose the very benefit of using a foundation like WordPress in the first place: maintainability.
We should use AI to accelerate our design systems, not to bypass them. The goal isn't just to move fast, it's to move fast without the house falling down in 6 months. Read the full post here: joost.blog/vibe-coding-tr…