Loading…
27
Hot take: I was building our component library wrong for a whole year
Honestly, I kept adding new, unique components for every feature request from the marketing team, which gave us over 80 separate buttons by last quarter. What tipped me off was our new dev, who asked 'why does this green button on the pricing page work differently than the green button in the dashboard?' and I couldn't give a straight answer. Has anyone else had to merge a ton of similar components and found a good way to explain the change to stakeholders?
3 comments
Log in to join the discussion
Log In3 Comments
nathang676mo ago
Hot take: Component hoarding.
Been there, done that, got the t-shirt. The real mess starts when you try to fix it and everyone says their special button is "part of the brand." You have to show them how much time and money it wastes just to change one color later. Frame it as making their future requests faster to build, not taking something away.
9
amy_reed797mo ago
Eighty different buttons sounds like a real headache.
6
lee87mo ago
Actually it's not that bad once you get used to it, @amy_reed79. The layout is pretty clear and groups things together. You just learn the main ones you need.
2