T
15

Just realized I was overcomplicating our component library

Honestly, I used to think every button needed 10+ props for every possible state. After our project in Austin last quarter, a junior dev showed me her simpler version with just 4 core props, and it cut our build time by 30%. Ngl, I was totally wrong. Has anyone else found that fewer options actually made your system more useful?
3 comments

Log in to join the discussion

Log In
3 Comments
briannguyen
But sometimes you really do need all those edge cases.
9
wadepalmer
wadepalmer11d ago
Depends on what you're building. Some libraries are simple until you hit that one client who needs a button that does sixteen things. Then you're back to square one.
4
jade618
jade6182mo ago
Totally feel you on the "10+ props" thing. I did the same with form inputs, making a crazy specific component for every data type. Tbh, cutting it down to a base component with like, three variants made the whole team actually want to use it.
2