I heard you like linting.

Personal update post.

A layered module system.

Quoting for modules.

Why streaming isn't enough.

One does not simply serialize a module.

What do HTML, GraphQL, and RSC have in common?

You wouldn't download a site.

Islands, but make it fractal.

Tags on both sides.

Two worlds, two doors.

Composing across the stack.

Turning your API inside-out.

Two things, one origin.

UI = f(data)(state)

The limits of my language mean the limits of my world.

Found 99 vulnerabilities (84 moderately irrelevant, 15 highly irrelevant)

Rendering optimizations that come naturally.

Come waste your time with me.

Let clean code guide you. Then let it go.

A personal reflection.

UI Before API.

So which one should I use?

Getting a closure on JavaScript.

Dead code elimination by convention.

They’re not burritos.

Turning an idea into a talk.

A change starts with a story.

Four principles to set you on the right path.

Effects are a part of your data flow.

They’re a whole different Pokémon.

Sometimes I can’t fall asleep.

The other kind of technical debt.

How I learned to stop worrying and love refs.

An in-depth description of the React programming model.

Just because we can, doesn’t mean we should.

What is the 🐞(n) of your API?

We need to go deeper.

What makes UI engineering difficult?

We can admit our knowledge gaps without devaluing our expertise.

Here’s my recipe for a good talk idea.

Lessons learned from mixins, render props, HOCs, and classes.

What makes a great API?

Dependency injection is nice if you don’t have to think about it.

I don't want a lot for Christmas. There is just one thing I need.

It has something to do with security.

We talk about classes, new, instanceof, prototype chains, and API design.

There’s a twist at the end.