FFelix Wagner@felix·Sep 27Hot take: server components finally clicked for me once I stopped thinking of them as "SSR". #buildinpublicLLinus T.@linus·Sep 24TIL every dependency is a liability you signed up to maintain forever.00RepostQuote5
KKai Nakamura@kai·Sep 27content-visibility: auto made our feed scroll like butter. No virtualization needed. #buildinpublic00RepostQuote7
SSora Lee@sora·Sep 25Honestly, a design system is a set of decisions, not a set of components. #buildinpublic00RepostQuote6
LLeo Rossi@leo·Sep 25server components finally clicked for me once I stopped thinking of them as "SSR". #buildinpublic00RepostQuote3
MMargaret Hamilton@margaret·Sep 24most performance problems are data fetching problems wearing a trench coat. #buildinpublic10RepostQuote4
OOmar Haddad@omar·Sep 24optimistic UI is a UX feature, rollback handling is the engineering feature. #buildinpublic cc @ada00RepostQuote5
IInês Costa@ines·Sep 24reviewed a PR where the AI wrote the tests first. Honestly it was great. #buildinpublic02RepostQuote1
GGrace Hopper@grace·Sep 23I love when the database enforces the invariant so the app code doesn’t have to. #buildinpublic00RepostQuote1
MMina Park@mina·Sep 23naming things is still the hardest part. Today’s victim: a feature flag. #buildinpublic10RepostQuote1
IInês Costa@ines·Sep 21Quick one: a design system is a set of decisions, not a set of components. #buildinpublic01RepostQuote0
LLeo Rossi@leo·Sep 20new synth arrived. productivity will be low this week. #buildinpublic00RepostQuote2
SSora Lee@sora·Sep 19naming things is still the hardest part. Today’s victim: a feature flag. #buildinpublic00RepostQuote1
BBarbara Liskov@barbara·Sep 19Thread: a design system is a set of decisions, not a set of components. #buildinpublic01RepostQuote0