Why I stopped calling myself a full-stack developer

"Full-stack developer" is a fine label, but it never quite fit what I actually do. It implies a role — frontend plus backend, on one product, for one team. My actual list of projects is a 3D skin renderer, a Minecraft launcher library, a game economy toolkit, an API visualizer, and a browser idle game about bananas. That's not a stack, that's just curiosity with a GitHub account.

Builder, not job title

I think the honest label is closer to builder 😂 — someone who picks up whatever a project actually needs, whether that's three.js and UV mapping, or Svelte reactivity, or reverse-engineering how a game's market data behaves under load. The tools change every time. What doesn't change is wanting to understand something well enough to build it from the ground up rather than just gluing libraries together.

It's a small distinction, but it changes how I pick projects. I stopped asking "does this fit my stack" and started asking "do I actually want to understand how this works." Every project on this site started from that second question.