CMColin Mak·Apr 700I'm looking for Full-time or Contract job opportunitiesAbout me: A full-stack developer with a love for solving complex problems through code, whether it's building immersive 3D web applications, developing decentralized blockchain platforms, or architectJoin discussion
BMBlaise Massa·Mar 1212Hi, I'm Blaise MassaI'm a frontend developer with experience in HTML, CSS, JavaScript, and Tailwind CSS. I am currently working on my personal project, a landing page. React is next! I'm interested in learning about becoFISyed and 1 more commented
RSRajdeep Singh·Mar 330Introduction & 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, Join discussion
SRSofia Rodriguez·Feb 2692Is 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, dSAShubham and 1 more commented
JMJake Morrison·Feb 2663React 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 requiremSARShubham and 2 more commented
SRSofia Rodriguez·Feb 2576What 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 ofSNMShubham and 5 more commented
JMJake Morrison·Feb 2510You 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 iJoin discussion
APAlex Petrov·Feb 2511Accessible 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 thCChloe commented
CDChloe Dumont·Feb 2500We 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 thJoin discussion
CDChloe Dumont·Feb 2564Semantic 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 spaNJNina and 3 more commented
