13 SYSTEMS / ONE PIPELINE
THE STACK.
Everything here is something I've shipped to production rather than a logo collected for a grid. Each page says what I use it for and where I think it stops being the right answer.
//Why write this down#
Because a list of technologies tells you almost nothing. Two engineers can both claim React and mean completely different things — one has built three dashboards, the other has spent a year on reconciliation behaviour under concurrent rendering. The useful information isn't what's on the list, it's what someone knows about the edges.
So each of these pages describes what I actually use the tool for, the specific thing I learned the hard way, and where I'd choose something else. That last part is the most honest signal available. Anyone who can't tell you when their favourite tool is the wrong choice hasn't used it on a project that pushed back.
//How the pieces fit#
In the common case: TypeScript as the language, React for component structure, Next.js when the project needs routing and server rendering, Tailwind for the token layer, and plain CSS wherever the abstraction stops paying for itself. Real-time work adds WebGL with hand-written GLSL, driven by a custom render loop rather than an animation library. Node sits behind it for the small amount of server work I take on.
The through-line is that I prefer fewer dependencies with deeper knowledge of each. Every library is a bet on someone else's maintenance and someone else's idea of the right abstraction, and the bets compound faster than most teams notice.