Schedule

I'm not here to tell you software engineering is ending soon. Nobody can put a reliable date on that, and pretending otherwise is a distraction. But we also have to admit something humbling: a year ago, most of us would not have predicted coding agents would be this good. That should make us less confident about predicting what they'll be able to do one year, or five years, from now.So let's use "The Last Software Engineer" as a thought exercise.

Many React developers use server rendering to improve performance. Before React 18, however, all four (4) steps in the server rendering process (data fetching, rendering to HTML, loading JavaScript, and hydrating) had to be completed for the entire app at once. This meant that a bigger or more complex part of your app would block other parts from moving onto the next step, making your app appear slower. Thanks to optimizations in React 18, you can use Suspense to break your app into smaller parts that go through these steps independently.

We all want software to run fast, and "performance" can include everything from network times to keyboard latency. But what about when you really do need Blazing Fast (TM) CPU speed from your code? How do you know what sections of your code are slow, _why_ it's slow, and how to make it faster?Like writing code and debugging, performance optimization is a skill set that anyone can (and should!) learn. We'll look at key concepts and approaches for profiling and optimizing CPU-level code performance, using real-world examples based on my experience optimizing the widely-used Immer JS library.

AI is changing how we build software. We can generate more code, faster, but we still have to live with the architecture, dependencies, and maintenance decisions that come with it. Open source still matters, and so does knowing when to use something that already works.In this talk, we’ll explore why a few words like “use TanStack” can save you time, effort, tokens, and heartache. Good defaults and proven libraries give you and your AI tools a shared foundation, so you can spend less time rebuilding common infrastructure and more time on what makes your application useful.

If I was perfectly comfortable with building single-page apps, what does migrating to server components actually do for me? Would it cost more? What could it actually do that wasn't possible before? And why was React going in this more complicated direction?

Vibe coding is easy, until you have to make an app that actually works. Sure, AI agents can spin up an impressive demo in minutes, but building a full-stack app that's robust, bug-free, and true to spec is where things get messy. And completely cloning an existing full-stack app? That's next-level difficult.

in this talk I’ll be exploring how agents have opened the doors to being able to create nearly anything you dream up. we’ll examine the intersection of ui/react/interfaces with hardware, both electronic and mechanical, and what that means for engineers moving forward.

Your agent is great at writing terrible code, and terrible at writing great code. I guarantee it. But with just a few guardrails (many of which we've already using for many years in industry), you can steer it from slop to splendor. We'll cover essential tips and tricks that I've been using for years in open source and this year as a frontend developer at Sentry, namely:* Skills: teach your agent how to do the common tasks specific to your stack and repository.* Static analysis: linting!

In recent years we've seen browsers deliver powerful APIs. What does this mean for the future of React development? A future with less JavaScript for interaction logic. In this talk we'll discuss new browser APIs released in 2026 and how you can leverage these new APIs and the impacts they will have on, application performance, developer experience, user experience, and the future of React app development.

Apple's first on-device foundation model gave developers a new execution path for AI features. iOS 27 expands what the system can do, while Android is moving in the same direction. If you last looked at this space around the initial release, the trade-offs and possible products have already changed.System-provided models have a distinctive place in the stack. They ship with the device, are optimized for its hardware, work offline, keep data local, and remove the need to package and maintain a model yourself.

A generation grew up with screens everywhere, and everyone assumed they'd show up as technology experts. Instead the tools got so easy that they never had to troubleshoot anything, and "digital native" stopped meaning anything. I think "AI native" is heading the same direction, and that's good news. If you're working right now, you're learning AI at the best possible time to learn it: it's good enough to change how you work and unreliable enough to teach you where it breaks, and you still have the fundamentals to tell the difference.This talk is about getting to the next level from wherever you're starting, when many of the technical skills that leveled up engineers in the past won't be enough anymore.

Self-hosting Next.js has always been easy... if you're willing to part with everything that makes it Next.js. ISR, image optimization, middleware at the edge, streaming, cache components—the features that sell the framework are the first casualties. That's changing.

Have you ever wondered why you reach for TypeScript? I hate TypeScript and use it every single day. In 2026, React developers live in TypeScript-land by default. Most templates ship with .tsx files, lots of job listings require TS experience, and yet somewhere along the line we stopped asking ourselves “Why should we use this tool?" TypeScript adds new and unique ways to trip yourself up.