There's a specific kind of developer shame nobody talks about.
It happens at 11pm. You're supposed to be finishing a feature. Instead, you're reading a Hacker News thread titled "Is Bun finally ready to replace Node?" and you have 14 tabs open — Bun's docs, a Reddit post comparing Deno vs Bun, a YouTube video you paused at 3 minutes, and a GitHub repo you starred but will never open again.
Sound familiar?
That was me. Every. Single. Month.
I spent the better part of three years in what I now call the shiny tool loop, a cycle of discovery, excitement, shallow learning, abandonment, and guilt. New framework drops? I'm on it. New AI coding assistant? Installed by lunch. New build tool that promises to be "10x faster"? Benchmarks read. Migration started. Migration abandoned.
My GitHub graveyard is full of half-migrated "test projects" with commit messages like chasing bun again and trying out astro (again).
Then, in late 2025, I burned out. Not dramatically, just quietly. I sat down to work one morning and couldn't remember why I'd started programming in the first place.
So I stopped. And I made a rule.
The Rule: Nothing New for 90 Days
No new frameworks. No new tools. No new AI assistants (yes, I had four installed at once). I would finish things with what I had.
It was uncomfortable for about two weeks. Then it got very, very quiet.
And in that quiet, I actually shipped things.
What I Kept (And Why)
Here's my stack going into 2026, chosen not because it's trendy, but because I can build almost anything with it without Googling the basics:
1. VS Code — still my main editor
I tried Cursor. I tried Zed. I tried going full Neovim for three weeks (don't). VS Code with a handful of extensions just works, has a massive plugin ecosystem, and I can pair it with any AI assistant I want. Stability > novelty.
2. Next.js — for anything that ships to users
Yes, the App Router has rough edges. Yes, I understand the React Server Components discourse. But Next.js has a gigantic community, excellent docs, and Vercel's deployment story is nearly effortless. When I'm building a product, I want to think about the product.
3. Claude / GitHub Copilot — as assistants, not crutches
This was the big mindset shift. I stopped using AI to write my code and started using it to review my code. I'll draft a function, then ask: "What edge cases am I missing?" or "How would you refactor this?" The quality of my output went up; the time I spent debugging AI-generated bugs went down.
4. Supabase — for anything that needs a backend fast
Postgres with a nice dashboard, auth built-in, and real-time out of the box. Not glamorous. Incredibly useful.
5. Plain CSS + Tailwind — I stopped framework-hopping here too
I used to switch between styled-components, CSS modules, Vanilla Extract, and Tailwind every few months. I picked Tailwind, learned it properly, and now I write UI fast. That's the whole story.
What I Actually Learned
The tools were never the problem. The problem was that learning a new tool feels like progress. It triggers the same reward center as actually shipping something, but without the hard parts. It's the intellectual equivalent of rearranging your desk instead of doing your work.
The developers I most admire aren't the ones using the newest stack. They're the ones who are dangerous with boring tools, who can build something meaningful with Next.js + Postgres + a bit of CSS faster than I could set up my seventh new monorepo boilerplate.
Mastery requires repetition. And repetition requires staying.
A Challenge for You
If you recognize yourself in that 11pm Hacker News tab spiral, try this: write down every tool you've "tried" in the last six months. Be honest. Now circle the ones you actually shipped something with.
That gap? That's the shiny tool tax.
Pick your core stack. Use it until it's boring. Then it gets interesting.
What's in your "I'm actually shipping with this" stack? Drop it in the comments, I'm genuinely curious whether the community is converging or fragmenting in 2026.
If this resonated, I write about developer productivity and building in public. Follow along, no newsletters, just posts when I have something real to say.
Top comments (0)