nater.dev ☀️

nater.dev ☀️

@nater-dev.bsky.social

I used to like computers

80 followers132 following80 posts

nater.dev ☀️ reposted

me knowing i’m not responsible for any php application right now

nater.dev ☀️ reposted

There’s a big difference between the promise of GenAI and the reality. The promise is the democratization of expertise. Anyone can be a coder, analyst or lawyer with AI. The reality is actually the erosion of expertise. Being an expert is no longer valued yet experts are needed to vet AI lies.

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

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.

Kelsey Hightower@kelseyhightower.com

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

PSA: The No Kings PAC is not affiliated with and had no role in putting on the 10/18 mobilization. If you get a spammy text from them claiming your donation will be 5x matched, know that it's not from anyone involved in the No Kings protest (and please direct your angry emails to them, not us)

nater.dev ☀️ reposted

it's kinda weird that all the software i am expected to use for work are all written by distributed teams, go, python, postgres, linux, chrome, k8s etc and despite being told "the best teams work in an office together" i don't know of any software i use that's actually written that way

“The moment you have nine useStates in a component, you've already shot yourself in the foot.” PREACH

Daniel Saewitz@saewitz.com

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

I want a normalized API pattern where introduction of a side-effect returns you a function to undo it. const controller = emitter.on('foo', cb) controller.abort() For everything, please. No more "and now let's call .removeListener() and provide the same fn by reference" 🤮

💯 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

Mark Erikson@acemarke.dev

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

As web devs we work on top of a huge pyramid of *extremely* good abstractions, from the metal on up. The problem with web dev currently is all the abstractions on top of HTML/CSS/JS/HTTP, by comparison, are quite leaky.

nater.dev ☀️ reposted

the tech market is so weird for entry level devs. it seems like no one wants to hire non-experienced devs, but you gotta get a job to get said experience, but the advent of AI makes companies not want to spend on entry level tasks, then eventually there will be no one to promote to seniors

It’s so easy to make a mess in React codebases. What makes React successful is that it’s also easy to hide those messes behind components and custom hooks. 🧹 This is called “sweeping it under the rug”

“Therefore, if you can’t easily make a mess go away, at least cordon it off. This restricts the disorder to a fixed area, keeps it out of sight, and can set the stage for additional refactoring.” How are you keeping your code tidy?

🎁 #React 19 is the gift that keeps on giving. We can finally drop useState in forms! With useActionState, you can streamline complex form logic into a single hook—no more scattered state updates. It can handle actions on the client OR server 🧑‍🍳💋 Have you tried useActionState? What do you think?

Setting state in useEffect? 🚨 That triggers a render loop: state changes→ render→ useEffect→ setState→ more renders. Instead, compute derived state directly—no loops, just clean, efficient code! #react

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

Marcin Milewicz@marcinmilewicz.bsky.social

🏗️ 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

🤔 Is React still the right choice for new apps in 2025? Alex Russell argues React’s abstractions, performance, and ecosystem are at odds with high-performing web experiences. He challenges engineers to ground technology choices in real user metrics rather than following trends

🤔 Is React still the right choice for new apps in 2025? Alex Russell argues React’s abstractions, performance, and ecosystem are at odds with high-performing web experiences. He challenges engineers to ground technology choices in real user metrics rather than following trends

The biggest disasters in system design often come from skipping one simple thing: a checklist. It’s far easier to spot what’s missing upfront than to scramble midway through development when something critical breaks. Here’s the checklist I swear by for designing systems:

View full thread

☑️ Detailed Design – The deep dive: * Backend changes * Frontend changes * Pattern deviations * Security * Performance * Analytics * Dependencies * Tech debt * Feature flags ☑️ Test Plan – How will we verify the system works as intended?

☑️ Unresolved Issues – Risks, blockers, and unknowns that could impact the implementation. ☑️ Document It – Write out each item in the checklist, fill it out, and share with your team for review This checklist has saved me countless hours (and headaches). What’s in yours?

The biggest disasters in system design often come from skipping one simple thing: a checklist. It’s far easier to spot what’s missing upfront than to scramble midway through development when something critical breaks. Here’s the checklist I swear by for designing systems:

☑️ Purpose – Why do we need this? What problem are we solving? ☑️ High-Level Design – A brief overview of the proposed implementation. ☑️ Alternative Designs – Other approaches, with pros and cons.

View full thread

In the code example, the ref callback receives the DOM node when the component mounts, allowing you to set focus immediately. This is especially useful for components like modals or loaders where you want immediate interaction.

Want to be seen as the go-to engineer in your team? It’s not about writing more code—it’s about reviewing it. Senior engineers don’t just write code—they shape the team’s success. 🧵

Here’s how: * Prioritize reviews over writing code. * Be approachable. Encourage others to ask for your feedback. * Think big. Focus on high-level design, not nitpicking. * Collaborate, don’t gatekeep. Your role is to share knowledge and elevate quality, not block progress.

When you do this consistently, you’ll become: * A trusted source of knowledge. * A key team collaborator. * A visible leader your manager will notice. The best engineers are known for their impact beyond their own code. How do you approach code reviews on your team? Share your strategies 👇

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”

Ricky@ricky.fm

normal render: - render - commit - effect with setState in useEffect: - render - commit - effect - render - commit - effect it’s a render waterfall

Instead, refactor so the state update happens during render. Many times, you can solve the problem without adding side effects at all. What’s your approach to minimizing useEffect in your React apps?