Hit 150 reusable component variants in my design system library and suddenly realized I'd created a monster

I was so proud of building out all those button states and icon sizes for our e-commerce checkout flow, but then I tried to onboard a new front-end dev and watching him scroll through 30 dropdown variations just to pick a simple input field made me question every life choice I've made, has anyone else accidentally over-engineered their library to the point it's less useful than starting from scratch?

2 comments

2 Comments

matthew_morgan23d ago

Have you tried locking down your core components and putting everything else in a separate experimental section? That’s what helped me when my library got bloated. I started treating the most used 20% as the real library and everything else as just extras you gotta dig for. You might also want to run a quick audit on what actually gets used in production versus what you just built because it looked cool. Trust me, cutting out the low usage stuff makes onboarding way less painful.

the_blake23d ago

Started doing exactly that a few years back when my own project was getting out of hand. I literally made a new folder called “core” and moved over the 10 or so functions that got called every single day, then shoved everything else into a “vault” folder no new dev even needed to peek at unless they got curious. Ended up trimming about 40% of the codebase once I actually looked at usage stats and saw stuff I wrote drunk at 2am never got touched. Made a mental note to kill any feature that didn't hit 5% usage over a couple months, and onboarding went from a two day nightmare to a quick afternoon chat.