What Ibet on
The stack I'll happily ship to production tomorrow morning. Everything on this page comes with an opinion — because the fastest way to slow a team down is to pick tools you can't defend.
The tools in almost every project I ship.
The backend I don't have to argue about
Eloquent, Postgres, Redis, queues. Boring — deliberately. When the framework isn't the interesting thing, I can spend attention on the product. And I can hand this stack to any senior on the team without a two-week onboarding.
Two front ends, one head
Vue 3 + Inertia when the API is Laravel. React + Next.js 15 when it's marketing or edge. Same taste, different tools — no religion, only fit.
TypeScript
Strict mode, no `any` in production. The compiler catches half the bugs before the tests do.
Tailwind CSS
The design system I don't have to negotiate. Tokens in @theme, no inline hex outside true one-offs.
Redis
The queue I trust with revenue. Also cache, session store, rate limiter, and pub/sub for Echo.
Every tech, honestly weighted.
Backend
Frontend
AI & Automation
Data
Infra & Delivery
Payments & Web3
Every dev has a stack list.
Few have a decision doctrine.
Six scenarios I've actually shipped. Tell me what you're building — I'll tell you what I'd reach for and why.
Growth is boring if I'm not learning something publicly.
Bun
Node compat with a runtime that gets out of the way. Currently benchmarking against Node on our Next.js builds.
tRPC
Type-safe client/server without hand-writing endpoints. Watching whether it earns the maintenance vs a plain REST layer.
Playwright Agents
Browser agents that survive real websites, driven by LLMs. Shipped Megaphone Swarm on this — expanding the pattern.

Ok so — what are you building?
You saw the doctrine. Now flip it. Tell me the constraints — team size, timeline, budget, existing stack, ceiling on the bill. I'll show you the picks I'd make and why.