Bear Design Systems

If I fart in the woods, is it a system contribution?

[Bear Design Systems @SystemsBear]

“We can’t use Web Components because I’m clutching my pearls! My precious Angular pearls!”

[Bear Design Systems @SystemsBear]

Using a 3rd party component library is not design systems.

[Bear Design Systems @SystemsBear]

“By introducing a new layer of Web Components to support our organization, you’re introducing complexity! We need to lower the quantity of technology stacks we use!”

Be not afraid, fellow compatriot, we are entering an era of massive AI complexity.

[Bear Design Systems @SystemsBear]

“I don’t want to use Web Componets because it’s hurts my developer experience feelings.”

Oh young cub, if only design systems were about the engineers, and not the end users.

[Bear Design Systems @SystemsBear]

I love when product people who don’t understand design systems tell me what to do.

[Bear Design Systems @SystemsBear]

“Design systems are so that all products can look the same.”

All forests do not look the same.

[Bear Design Systems @SystemsBear]

“PrimeNG and Shadcn are web components”

Said every tech lead who doesn’t understand the Web.

[Bear Design Systems @SystemsBear]

“Design systems coders should also adopt design systems in product code.”

Barf on a stick. 🤮 🌲

[Bear Design Systems @SystemsBear]

Nothing marks the death of a design system more than hosting office hours and nobody shows up. Nobody.

[Bear Design Systems @SystemsBear]

Hell hath no fury like my rage for the engineer who came in and blew away our entire repo of Web Components so we could reuse existing “battle tested” old Angular Material components, which upon further inspection, are a steaming pile.

[Bear Design Systems @SystemsBear]

All I hear are people who don’t understand design systems talking about design systems.

[Bear Design Systems @SystemsBear]

“When will logos be available from the design system?”

How about never.

[Bear Design Systems @SystemsBear]

A single person having the thought “this should go in the design system” does not mean it should go in the design system.

[Bear Design Systems @SystemsBear]

“Let’s use one product’s existing set of components, because adoption is already done.”

Said every non-systems thinker, ever.

[Bear Design Systems @SystemsBear]

Yesterday someone referred to this design system as “your project”.

‘Tis true, I am the only bear in this forest.

[Bear Design Systems @SystemsBear]

Rolly polly time!

Should design systems change every time a design manager looks at the Figma file?

[Bear Design Systems @SystemsBear]

Reviewing our component API across code & design, and it’s making me cry a little on the inside. #emptystate

[Bear Design Systems @SystemsBear]

Every engineering manager I’ve encountered working on design systems says something like “I’m the decision maker here. What I say goes.”

Rather than being inclusive and providing safe space for the whole team to voice their opinions. I’m going to start calling them Baby Bears.

[Bear Design Systems @SystemsBear]

“I just added a suffix to this component because it has a prefix and it just felt right.”

Nice job, Cochise.

[Bear Design Systems @SystemsBear]

@elonmusk I also find uncanny things.

https://t.co/o7tCmVuz80

[Bear Design Systems @SystemsBear]

I'm an unopinionated bear. I watched the news for the first time last night. Here's my unopinionated opinion.

Elon Husk: A shell of the former genius.

Understands any publicity is good publicity.
Understands deregulation is good for his businesses.
Zero morality.#TrumpRally