3 ms·

Reusable components of any nontrivial complexity are, for the most part, a pipedream. Unless you have a dedicated team maintaining and extending them, it immedi

Reusable components of any nontrivial complexity are, for the most part, a pipedream. Unless you have a dedicated team maintaining and extending them, it immediately becomes more of a hassle than anything. Documentation is slim, edge cases aren't completely thought through, and configuration is never sufficient. Visual design patterns can absolutely be standardized. But the actual implementation as we all know changes ever so slightly from project to project in ways that can almost never be forseen. I'm all for component driven UI architectures, but the idea of being able to reuse anything complex between projects and teams has never really worked out in my experience unless it is a highly active open source project, or something you built yourself and fully understand.

yurishimo 7y ago
This is so true. I have a junior developer who is hellbent on extracting little chunks of things to be “reused” on future projects but we work at a marketing agency that does a lot of bespoke design. Sure, sites might have a collapsible FAQ section, but when the design is so wildly different from project to project, it takes more time to overwrite things than to start from scratch and write the 3 lines of jquery to get the section to toggle open and close. I totally understand component driven UIs but marketing outside of generic landing pages is not a productive area to spend your time creating abstractions.