Nathanael Bennett

“React was such a good idea that we will spend the rest of the decade continuing to explore its implications.” - Guillermo Rauch One of the things I like about React and SwiftUI is how the declarative model makes it abundantly clear that UI data is simply…

Preface - Why are we still talking about OOP?

When modeling the behavior of data, we usually start by treating a concept either as data inside a system of functions, or as data coupled with behavior in a polymorphic hierarchy.

DPC wrote a great blog post about how you can’t just avoid complexity.

I know Rust is still pretty niche, so consider this piece of idiomatic Typescript: const client = this.clients.get(user_id); if (client) { client.status = ClientStatus.Disconnected; } A Rust version: self.clients.get_mut(&user_id).map(|client| {

https://www.rfleury.com/p/programmers-are-users-bad-performance I thought this was a really well written piece describing some of the unforeseen consequences of optimizing toward DX.

State management considered harmful One of the most exciting things about working in the React ecosystem is you can observe, almost in real time, how our perspective on the problem domain of UI development evolves.

I’m currently building a browser-based multiplayer game using WebRTC, authoritative servers, and HTML5.

When I first encountered Scrum, I liked the idea.

There’s a famous story about Bill Atkinson where management asks everyone to account for how many lines of code they wrote each week.

One of the things I love about Rust is the ubiquity of pattern matching.