Take all the advice from frontier labs with a huge grain of salt. By design or not, their workflows assume you're ok spending a ton of tokens.
Having a 24/7 always-on agent sounds great in practice. Look ma! I pushed a bajillion PRs today!
Don't lose track of your outcomes.
The biggest obstacle to replace GitHub is the Actions ecosystem not Git.
In an agentic world, carefully maintained YML files will disappear, but I haven’t seen anyone do this elegantly.
GitLab is doing the opposite, use AI to migrate your workflows into a crappier YML file. 👎
The Bun rewrite and TanStack inspired me to do what I've been waiting for, literally years, in Next/React.
In Next, the lifecycle hooks of _document in App Router. i.e., let me hook up RSC + server rendering before flushing the initial chunk. 🙌
In React, unlock RSC context! 🙏
To support the RSC context, all React needs to do is allow exporting getServerTreePath, and the rest can be done in userland.
React already has `currentlyRenderingTask` internally. Can't fit the whole patch in a screenshot, but you get the gist.
I’d honestly pay a premium for a movie theater experience where people are required to put their phones in a faraday cage bag.
I’m sure the Alamo Drafthouse figured out it’s easier/cheaper to have someone monitor, but one can hope @AMCTheatres 🙏
Wait, so Turbopack has no Plugin API or plans to do so? For some reason, I thought babel plugins was the dealbreaker from early on, but no compilation hooks at all? Huge bummer.
Finally caught up on Remix 3, and it's incredible.
The holy trinity of Events, Signals, and Frames as primitives are *chef-kiss* abstractions.
It's pretty rough, but VERY promising. Their biggest challenge IMO is people's preconceived ideas from Remix's/React-Router's past.
I had the opportunity to share some insights from my experience in scaling AI workflows and usage across the org @Hearst with some practical advice for engineering leaders.
Thanks to @ladyleet @robocell for the invite!
There are a few things that I hate more than a PR that is ready to be merged (whatever that entails), that is not merged, and live in production.
Every second that passes is an infrastructure failure.












