how years of building eventually pushed me to create my own web stack
I’ve been building for a long time. started doing paid web work back in the late 90s, lived through multiple waves of frameworks, libraries, architectural trends, and pretty much every major shift in the web ecosystem. over the years I worked with a lot of great tools, but I kept running into the same feeling that simple things were becoming harder than they needed to be
it wasn’t that the frameworks were bad. most of them solved real problems. but after enough projects, enough production systems, and enough tradeoff conversations, I started wanting something that fit the way I think about software more closely
what changed things for me was bringing Blackbox AI into the process. instead of just experimenting blindly, I started using it to compare patterns across frameworks, validate architecture decisions, stress test ideas, and challenge assumptions I had built up over years of experience
that eventually led me to building my own micro stack. something lightweight, built around web standards, minimal dependencies, server and client support, SSR, static generation, and hybrid rendering when needed. no unnecessary abstraction, no fighting the framework, just a system designed around what I actually value after decades of shipping software
the surprising part is not that I built it. it’s that it’s now running in production across real projects and solving the exact problems I wanted it to solve
now I’m at the stage where I’m thinking less about whether it works and more about how to share ideas like this in a world where attention moves faster than technical depth
curious if anyone else here has reached a point in their career where building your own tools or systems started making more sense than constantly adapting to everyone else’s stack, especially now with tools like Blackbox AI accelerating how quickly those ideas can actually become real
Posted May 2, 2026, 4:29 AM UTC