nater.dev ☀️
nater.dev ☀️ reposted
nater.dev ☀️ reposted
nater.dev ☀️ reposted
nater.dev ☀️ reposted
We have the right to record ICE agents, police, and other government officials at work in public. Read up on your rights and our tips to get ready for Saturday's No Kings protests. More info at aclu.org/kyr_record-
nater.dev ☀️ reposted
nater.dev ☀️ reposted
Some people can't afford the cost of a Real ID, or a copy of their birth certificate, which is why it's important for those of us who can help to help. Even helping just one person goes a long way. This is about preparation for any foolishness while we continue to fight for our right to vote.
Games are being played with your right to vote. I know it's not possible for everyone, but I'm making sure I got all my paper work in order. Voter registration, certified copies of my birth certificate, Real ID, and U.S. passport. And the start of early voting is marked on my calendar. No excuses.
nater.dev ☀️ reposted
nater.dev ☀️ reposted
“The moment you have nine useStates in a component, you've already shot yourself in the foot.” PREACH
the highest number of useStates I have in a component is 3. Most have one or two. I have never thought about that until right now, it's just that you should never really need more than 2-3 in a component. The moment you have nine useStates in a component, you've already shot yourself in the foot.
nater.dev ☀️ reposted
nater.dev ☀️ reposted
AI-assisted coding for teams that can't get away with vibes blog.nilenso.com/blog/2025/05...
💯 it isn’t clear from the docs how to roll your own RSC implementation which is pretty important for developing a strong intuitive understanding of the technology
my own thought from the sideline is that the lack of concrete "how do I adopt / migrate this" info and capability is a bigger blocker for the ecosystem than "what problems does this solve".
nater.dev ☀️ reposted
nater.dev ☀️ reposted
nater.dev ☀️ reposted
nater.dev ☀️ reposted
Stop overusing useEffect for DOM tweaks! In React 19, the ref callback cleanup lets you handle DOM side effects directly. But don’t take it from me… @tkdodo.eu wrote a great post about it: tkdodo.eu/blog/ref-cal...
I think this is why @shadcn.com has become so popular. It puts you in control of the component contract without sacrificing the convenience of a complete implementation
🏗️ Frontend Arch Note #14: Shared component libraries are distributed coupling. Each reused component is a contract. Each contract needs maintenance. Choose your dependencies carefully. #Frontend
nater.dev ☀️ reposted
Most of the time, useEffect *is* the wrong choice. One common mistake: using it to set or update state. This creates unnecessary re-renders and leads to a “render waterfall”
normal render: - render - commit - effect with setState in useEffect: - render - commit - effect - render - commit - effect it’s a render waterfall
nater.dev ☀️ reposted