AI keeps coming up at work, but you still don't get it?

That's exactly why 1M+ professionals working at Google, Meta, and OpenAI read Superhuman AI daily.

Here's what you get:

Join 1M+ pros

🧠 React Server Components support without a framework
A new tool called Forket makes it possible to use React Server Components (RSC) without being tied to a framework like Next.js. It works by splitting code into server and client parts at build time, handling hydration and server actions with minimal setup. Forket builds a component graph, identifies boundaries, and injects the glue code needed to stream and hydrate components, all while staying framework-agnostic.

🏃 Using Activity with Suspenseful data
This post explores how React 19’s experimental <Activity> component helps manage component visibility without fully unmounting them. It highlights scenarios where hidden components continue suspenseful data fetching, maintain local state, and unmount effects, ideal for cases where visibility logic lives inside child components. Compared to filtering or bulk-fetching in the parent, <Activity> offers a more nuanced and performant approach for dynamic UIs.

🪟 react-window v2.0 is out
React Window v2 is out now with several key improvements: a more ergonomic props API, automatic memoization for renderers, built-in auto-sizing for List and Grid, native TypeScript support, and a smaller bundle size.

💡 What’s new in react 19 that is useful?
In this Reddit thread, developers discuss what’s actually useful in React 19. While React Server Components (RSC) got a lot of attention, many found more value in removing the need for forwardRef, the introduction of the use() hook, and cleaner typing via ComponentProps<>. Others highlighted the React Compiler, which reduces the need for memo, useMemo, and useCallback, and praised new form handling features like useActionState.

😠 Next.js Is Infuriating
In this blog, Dominik vents frustration over Next.js’s limitations, especially around logging and middleware. Despite attempts to use AsyncLocalStorage and Pino for structured logging, the restrictive middleware design and lack of consistent async context made it nearly impossible to log effectively across middleware, pages, and client components. The piece ends by comparing Next.js unfavorably to SvelteKit and calling out long-standing unresolved issues on the Next.js GitHub repo.

Quick Links

🗺 A staff engineer's 6-week journey with Claude Code
In this blog, a staff engineer shares a six-week deep dive using Claude Code to accelerate development. By treating AI like a junior dev with no memory, they outline a practical workflow of iterating through messy first drafts, layering in project context, and managing multiple agents. The post covers real-world benefits, like faster shipping and code review strategies, as well as challenges like lack of memory, hallucinations, and cost.

🧑‍💻 Cosden Code Waitlist
A new kind of platform where expert-crafted React courses meet intelligent, AI-powered guidance. Human-designed, AI-delivered. The waitlist is now open, and I will be selecting people to beta test shortly!

💼 AI and jobs, again
In this post, Noah Smith breaks down conflicting research on whether AI is actually costing people jobs. One study finds no major impact, while another links AI exposure to declining employment among young workers. But the data raises questions, why would AI affect 22-year-olds but not 40-year-olds doing the same job? Noah urges skepticism, arguing we still don’t really know what AI is doing to the labor market, and likely won’t for a while.

🪤 Traps to Developers
This post offers a massive, practical roundup of developer "traps" across dozens of domains. From CSS quirks and Unicode gotchas to floating point edge cases, middleware caveats, Git pitfalls, SQL deadlocks, and more, it’s a dense catalog of unintuitive behaviors that commonly cause bugs. If you’ve ever been blindsided by layout collapse, precision errors, or unexpected async behavior, there’s probably a section for that.

💾 Use One Big Server
This post argues that for most web services, one big server is often simpler, cheaper, and more performant than complex cloud-native architectures. It breaks down the real capabilities of modern hardware, compares costs across providers, and highlights how cloud premiums can exceed 5–25x. While cloud services offer flexibility and burst scaling, for steady workloads, “tall” vertical scaling with fewer, larger servers often wins.

In this video, we'll review code written by a junior developer that has room for improvement in several key areas. We'll examine everything from fundamental JavaScript concepts, like variable naming and coding conventions, to flawed system designs that require additional patches to fix bugs caused by poor architectural choices.

This developer has plenty to learn, and that's perfectly fine. That's exactly why I create these videos!