Can You Ship Vibe-Coded Software to Production?
Vibe coding lowers the cost of a first version, not the cost of being wrong. That bill arrives in production, not at build time.
Tag
31 entries: Note, System, Essay.
Vibe coding lowers the cost of a first version, not the cost of being wrong. That bill arrives in production, not at build time.
Why the classic layered structure is enough for most projects while we drown in abstraction layers, and when Clean Architecture actually pays off.
Applying YAGNI in practice: the price of adding flexibility you don't need today, repaid daily in maintenance, readability, and bug surface
Generating legally sequential, gap-free numbers with parallel workers: the JIT reservation pattern that solves race conditions and gaps together
The measured signals that justify moving from a monolith to a distributed architecture — and the common false reasons that say it's still too early
The case for drawing clean module boundaries inside a single deployable app before jumping to microservices — and when I stop doing it.
As data load grows, where does boring architecture break? Working set, read replicas, partitioning, write load, a separate data layer — in order.
The pragmatic case for choosing proven tools over chasing new technology. This is not cowardice, it is a budget decision.
The pattern I use to avoid key collisions and accidental deletes when a single Redis instance is shared across several projects
One VPS, several independent apps. Deliberate minimalism over Kubernetes: user isolation, separate PHP-FPM pools, shared PostgreSQL/Redis, a plain deploy.
A production-grade Laravel setup with Nginx + PHP-FPM + Redis + PostgreSQL + Supervisor + Horizon. Each piece's job and what you lose if you drop it