惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Vercel News
Vercel News
O
OpenAI News
Engineering at Meta
Engineering at Meta
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
月光博客
月光博客
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
WordPress大学
WordPress大学
宝玉的分享
宝玉的分享
GbyAI
GbyAI
T
The Blog of Author Tim Ferriss
Google DeepMind News
Google DeepMind News
B
Blog RSS Feed
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
云风的 BLOG
云风的 BLOG
罗磊的独立博客
S
SegmentFault 最新的问题
The Register - Security
The Register - Security
Hugging Face - Blog
Hugging Face - Blog
D
DataBreaches.Net
U
Unit 42
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
B
Blog
阮一峰的网络日志
阮一峰的网络日志
P
Proofpoint News Feed
雷峰网
雷峰网
V
Visual Studio Blog
小众软件
小众软件
aimingoo的专栏
aimingoo的专栏
N
Netflix TechBlog - Medium
酷 壳 – CoolShell
酷 壳 – CoolShell
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Y
Y Combinator Blog
博客园 - 【当耐特】
G
Google Developers Blog
L
LangChain Blog
Stack Overflow Blog
Stack Overflow Blog
I
InfoQ
Martin Fowler
Martin Fowler
F
Fortinet All Blogs
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
The Cloudflare Blog
AI
AI
Google Online Security Blog
Google Online Security Blog
Hacker News - Newest:
Hacker News - Newest: "LLM"
博客园 - Franky
Blog — PlanetScale
Blog — PlanetScale
Webroot Blog
Webroot Blog
PCI Perspectives
PCI Perspectives
爱范儿
爱范儿
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org

overreacted — A blog by Dan Abramov

There Are No Instances in atproto — overreacted Algebraic Effects for the Rest of Us — overreacted A Social Filesystem Introducing RSC Explorer — overreacted Hire Me in Japan — overreacted How to Fix Any Bug — overreacted Where It's at:// — overreacted Open Social A Lean Syntax Primer — overreacted Beyond Booleans — overreacted The Math Is Haunted — overreacted Suppressions of Suppressions — overreacted How Imports Work in RSC — overreacted RSC for LISP Developers — overreacted Progressive JSON — overreacted Why Does RSC Integrate with a Bundler? — overreacted One Roundtrip Per Navigation — overreacted Static as a Server — overreacted RSC for Astro Developers — overreacted Functional HTML — overreacted What Does "use client" Do? — overreacted Impossible Components JSX Over The Wire React for Two Computers The Two Reacts — overreacted A Chain Reaction — overreacted npm audit: Broken by Design — overreacted Before You memo() — overreacted The WET Codebase — overreacted Goodbye, Clean Code — overreacted My Decade in Review — overreacted What Are the React Team Principles? — overreacted On let vs const — overreacted What Is JavaScript Made Of? — overreacted How Does the Development Mode Work? — overreacted Preparing for a Tech Talk, Part 3: Content — overreacted Name It, and They Will Come — overreacted Writing Resilient Components — overreacted A Complete Guide to useEffect How Are Function Components Different from Classes? — overreacted Coping with Feedback — overreacted Fix Like No One’s Watching — overreacted Making setInterval Declarative with React Hooks — overreacted React as a UI Runtime Why Isn’t X a Hook? — overreacted The “Bug-O” Notation — overreacted Preparing for a Tech Talk, Part 2: What, Why, and How — overreacted The Elements of UI Engineering — overreacted Things I Don’t Know as of 2018 — overreacted Preparing for a Tech Talk, Part 1: Motivation — overreacted Why Do React Hooks Rely on Call Order? — overreacted Optimized for Change — overreacted How Does setState Know What to Do? — overreacted My Wishlist for Hot Reloading — overreacted Why Do React Elements Have a $$typeof Property? — overreacted How Does React Tell a Class from a Function? — overreacted Why Do We Write super(props)? — overreacted
I'm Doing a Little Consulting — overreacted
2025-06-11 · via overreacted — A blog by Dan Abramov

It’s been a while since I’ve posted any personal/professional updates.

As some of you might know, I left Meta in July 2023. I wanted to take a long break from work around then—but I got excited about Bluesky being at the intersection of all my interests (React, open source, being addicted to Twitter) and I’ve spent the next (almost) two years there. I’ve learned some of the ins and outs of React Native, helped the team get the app a lot more polished, and also did a little bit of engineering management. Then I realized I actually needed a long break, and it could not wait any further. So I left and have been free-floating for a few months.

I’m in-between things now. It’s a weird time because I don’t understand what’s going to happen to my skillset. Both in terms of actual software engineering and in terms of teaching people. How both of these things get done is evolving. I don’t know where my field is going, and I don’t have an obvious “next” thing that I want to do. So for now I’ll sit by the river and watch whatever’s happening float by.

I’ve revived this blog. Mostly writing about React Server Components because I had a bunch of things I wanted to be able to point people to that had no definitive URLs. I’m not sure if I’m running out of posts yet. There’s a few more things I’d like to write about—like atproto and Lean—but I can’t quite get into the mindset of moving on from RSC writing. Maybe I need to fully exhaust that stream first.

Anyway, per the post title—I’m doing a little consulting now.

I’m not writing code, but if you or your team need some technical guidance in UI engineering (my expertise is mostly around React and React Native), I may be able to help. We can talk about your architectural challenges, performance challenges, dive deep into specific technical issues, or talk about higher-level approaches to product and infra development. I’ve been lucky to work with great engineers at both Meta and at Bluesky, and I enjoy the chance to pass on what I’ve learned.

The format is a 1:1 hourly call. We can do a single one at first, and extend to several sessions if you find it beneficial and/or want to follow up. This will probably work best for technical leaders (or very motivated learners). It is unfortunately not free (somebody asked me that so I have to clarify). If this sounds interesting, drop an email at [email protected], and I’ll reply if I can help.

Thanks!