News for hackers. Stuff that matters.
Re:Why and How We Retired Elm at Culture Amp by tomca32 on Saturday April 08, 2023 @03:41PM (#35496855)
> Culture Amp was well on its way to doing this in 2018, when things started to get hard for the recently-formed Design System team.

This is the problem right there. Design system teams never work well. A design system that’s complicated enough to need a dedicated team always creates more friction than it’s worth. Turns out that it’s really hard to standardize UI components in a way that makes them flexible enough to be used across different teams.

The only design systems I’ve seen work well are the minimal ones that just define the color values of the visual theme and look of some basic components like buttons but leave the implementation up to the individual devs.

Re:Why and How We Retired Elm at Culture Amp by epolanski on Saturday April 08, 2023 @04:27PM (#35497281)
Hmm, that's not true?

GitHub, Atlassian, Microsoft, plenty of greatly and widely used design systems out there.

The problem is different: they are huge investments that most non-large companies cannot afford for economic and logistic reasons.

Re:Why and How We Retired Elm at Culture Amp by the_gipsy on Saturday April 08, 2023 @06:48PM (#35498413)
But those companies are several leagues higher than whatever Culture Amp is.
Re:Why and How We Retired Elm at Culture Amp by joneil on Monday April 10, 2023 @09:29AM (#35512040)
I work at Culture Amp and was once team lead of the Design System team.

Its not hard to justify the team. If 4 front end engineers in a design system team can solve some common problems (writing components, improving accessibility of existing components, writing docs, answering technical questions etc) in a way that makes 40 product facing front end engineers more effective than 44 who don't have access to the team... then the team is a net positive.

At our scale we'd need to give a 10% improvement in efficiency to the product engineers. Both the engineers in product teams, and the various levels of leadership, have seen enough to believe we're making at least that much of a difference. Like almost any other company... measuring that accurately is a nightmare (and would require a significantly larger team just to measure ) but its a safe enough bet that we continue to invest in it.

Re:Why and How We Retired Elm at Culture Amp by the_gipsy on Wednesday April 12, 2023 @07:32AM (#35537989)
The problem, with something like a Design System and many other aspects of organizational management, is that efficiency measuring tends to ignore the overhead, the death by a 1000 papercuts, and only focuses on the sweet points.
Re:Why and How We Retired Elm at Culture Amp by brahbrah on Sunday April 09, 2023 @08:34AM (#35502137)
Just speaking it off my ass here, but it could be the scale of those companies that make those teams viable. Like let’s say you have some standardized systems that can cover the use cases of 20% of your teams. If you have 1000 teams vs 10 teams, covering 200 teams might make economic sense, but 2 teams wouldn’t
Re:Why and How We Retired Elm at Culture Amp by marcelr on Saturday April 08, 2023 @05:47PM (#35497959)
I’ve seen this at 2 companies so far and tend to agree. At this point if your design system requires more than css its probably too complicated.

Maybe design systems work when you are the size of google, etc, but otherwise they are way more work than people seem to believe.

Re:Why and How We Retired Elm at Culture Amp by joeblubaugh on Saturday April 08, 2023 @08:21PM (#35498956)
There’s also the part where they just let teams get away without fulfilling their responsibility to update both versions of a component and just let their tech degrade.
Re:Why and How We Retired Elm at Culture Amp by JackMorgan on Sunday April 09, 2023 @06:41AM (#35501458)
I'm at the point now where I think a design system team is a huge anti pattern unless you have a company with thousands of developers. I've seen three different companies throw hundreds of person years into building out design systems, each to eventually throw it all out. By this time many teams have been forced to adopt the half finished project, so now they've got to tear it all out.

We all know now not to build our own databases. Design systems are similarly so hard to get right I suspect in another decade or two we'll say the same thing about design systems.

There's nothing wrong with some CSS colors and basics. But you'll only invite ruin if you try to build out (or wrap) React or Angular libraries. I'd guess right now that a full design system like that would take a hundred person years to complete. By which time the target library will likely have changed so much you'll have to start over at the beginning and start upgrading.