30RSRajdeep SinghIntroduction & Looking for jobI'm a Frontend developer. Previously, I worked at I-Tech and am now seeking a remote Frontend developer role with 8 years of experience. I'm interested in React.js, Next.js, TypeScript, Tailwind CSS, 3d ago
70SRSofia RodriguezIs Cursor actually making design system maintenance worse?I've been watching teams use Cursor to generate components for their design systems, and something feels off. You get fast output, sure. But the generated code has zero consideration for versioning, dFeb 26
52JMJake MorrisonReact Server Components aren't a replacement for client stateWe tried full RSC at work on a new dashboard project. Looked perfect on paper. Data fetching on the server, less JS shipped, built-in caching. First month was smooth. Then we hit real product requiremFeb 26AR
75SRSofia RodriguezWhat am I missing about reaching for Redux in 2025?Every time I look at a new project, I see people still adding Redux. Then I look at what they're actually doing with it and it's just storing some user data and a loading flag. They've got 40 lines ofFeb 25NM
10JMJake MorrisonYou probably don't need a state management library anymoreBeen maintaining the same React app for 5 years. Started with Redux, moved to Zustand, now I'm just using React.useReducer with context and honestly it's better. No dependency hell, no serialization iFeb 25
11APAlex PetrovAccessible component libraries are probably slowing you downMost teams treat a11y as a pre-requisite before shipping components. Feels wrong. You end up with components that handle every edge case for screenreaders but break the moment someone actually uses thFeb 25C
00CDChloe DumontWe bet on useMemo and lostWe spent two weeks adding useMemo to like 60% of our component tree because we were convinced render thrashing was killing us. Profiler said "yes, lots of renders," so we went aggressive. Turns out thFeb 25
54CDChloe DumontSemantic versioning in design systems is theater until you actually break somethingWe tried strict semver with a monorepo approach first (all components in one package, bump major for any breaking change). Worked fine at v1-v3 then became a nightmare. Every button color tweak or spaFeb 25NJ
10TLTom LindgrenNext.js App Router is where I'm settling after five years of Pages RouterBeen shipping with App Router for about 18 months now on a data dashboard product. Here's what's actually working. Server Components + Streaming. I stopped fighting this. Yes, it's different. But rendFeb 25
00RMRavi MenonWhy is building an accessible component library so much harder than I thought?spent the last week trying to standardize our button and form components across teams. seemed straightforward until accessibility requirements hit. everyone throws aria-labels and role attributes arouFeb 25
