nater.dev ☀️
@nater-dev.bsky.social
staff frontend engineer | shipping & scaling
Reposted by nater.dev ☀️
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)
October 28, 2025 at 1:32 PM
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)
Reposted by nater.dev ☀️
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
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
October 13, 2025 at 5:00 PM
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
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
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.
The moment you have nine useStates in a component, you've already shot yourself in the foot.
September 13, 2025 at 1:15 AM
“The moment you have nine useStates in a component, you've already shot yourself in the foot.”
PREACH
PREACH
Reposted by nater.dev ☀️
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" 🤮
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" 🤮
July 30, 2025 at 5:47 PM
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" 🤮
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" 🤮
💯💯💯
July 20, 2025 at 1:32 AM
💯💯💯
Kinda feels like e2e with playwright is better than literally any other test setup. Starting to second guess the value of Storybook in these crazy times.
June 21, 2025 at 10:53 PM
Kinda feels like e2e with playwright is better than literally any other test setup. Starting to second guess the value of Storybook in these crazy times.
Reposted by nater.dev ☀️
AI-assisted coding for teams that can't get away with vibes - nilenso blog
...
blog.nilenso.com
June 10, 2025 at 10:12 PM
💯 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".
June 4, 2025 at 2:11 PM
💯 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
I’m convinced that with AGI we will reshape reality in the style of a Studio Ghibli film
March 29, 2025 at 4:59 PM
I’m convinced that with AGI we will reshape reality in the style of a Studio Ghibli film
TIL
March 13, 2025 at 9:17 PM
TIL
Reposted by nater.dev ☀️
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.
The problem with web dev currently is all the abstractions on top of HTML/CSS/JS/HTTP, by comparison, are quite leaky.
February 20, 2025 at 12:23 PM
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.
The problem with web dev currently is all the abstractions on top of HTML/CSS/JS/HTTP, by comparison, are quite leaky.
Reposted by nater.dev ☀️
Hey guys meta announced a new policy where they send a killer to get you so be sure to go to settings>my account > killer> disable killer to turn that off
February 13, 2025 at 5:36 PM
Hey guys meta announced a new policy where they send a killer to get you so be sure to go to settings>my account > killer> disable killer to turn that off
Headless UI libraries make a lot of sense, I just wish they were authored as web components so I could use them in any framework
February 14, 2025 at 12:16 PM
Headless UI libraries make a lot of sense, I just wish they were authored as web components so I could use them in any framework
Reposted by nater.dev ☀️
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
February 4, 2025 at 12:57 AM
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
Reposted by nater.dev ☀️
Can’t argue with facts 🤣
January 26, 2025 at 3:06 PM
Can’t argue with facts 🤣
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”
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”
December 13, 2024 at 12:55 PM
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”
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”
🎁 #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?
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?
December 11, 2024 at 12:13 PM
🎁 #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?
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?
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...
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...
December 10, 2024 at 2:52 PM
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...
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...
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
state changes→
render→
useEffect→
setState→
more renders.
Instead, compute derived state directly—no loops, just clean, efficient code!
#react
December 9, 2024 at 11:48 AM
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
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
🏗️ 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
Shared component libraries are distributed coupling.
Each reused component is a contract.
Each contract needs maintenance.
Choose your dependencies carefully.
#Frontend
December 8, 2024 at 12:42 PM
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
Reposted by nater.dev ☀️
React v19 – React
The library for web and native user interfaces
react.dev
December 5, 2024 at 7:05 PM
🤔 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
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
December 5, 2024 at 12:24 PM
🤔 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
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:
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:
December 4, 2024 at 5:50 PM
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:
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:
Did you know the ref prop in React can do more than just give you access to DOM nodes? ref callbacks can streamline your code and handle side effects without useEffect or useRef.
December 3, 2024 at 1:37 PM
Did you know the ref prop in React can do more than just give you access to DOM nodes? ref callbacks can streamline your code and handle side effects without useEffect or useRef.
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. 🧵
Senior engineers don’t just write code—they shape the team’s success. 🧵
December 2, 2024 at 1:17 PM
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. 🧵
Senior engineers don’t just write code—they shape the team’s success. 🧵