I was watching Casey Muratori and the Primeagen the other day, and they were talking about the high-level architectural design of the core data inside of Primeagen's game. What Casey says sounds counter-intuitive for anyone from a traditional OOP software background. He suggests not committing to an organization of data

Just like CAD didn't make everyone an industrial designer, visual programming isn't going to make everyone a programmer. Whether textual or visual, there'd still be a lot of underlying concepts (and how they are composed) to learn. But still, I think it's underexplored. Most visual programming paradigms focus on coding--the

💡The Recurse Center encourages recent graduates to write about their experience in the form of a Return Statement. Below is mine. The 12-week experience at RC did remind me of the story of the tall, strong, and unbendable Oak that towers over the short, thin, and flexible Reeds. On an

👉When I had mistakenly thought that Prolly Trees weren't unict [https://interjectedfuture.com/lab-notes/lab-note-030-the-trick-to-unicity-of-prolly-trees/] , I thought maybe an interesting way forward was to leverage the same mechanism CRDTs use to converge. Below is a mathematical description of what I called a Lattice Merkle Tree, still incomplete. I had time-boxed

I was surprised to learn that different stacks of software all do some type of computational analysis to better do its job. The CPU does it to figure out how to pipeline instructions. Compilers do it to feed CPUs better set of instructions. Front-end frameworks do it to figure out

As an exercise to see what the developer experience might look like, I outlined what it might look like for a React-like single-page app. The app that's outlined below is a variation on the TodoMVC.