All Posts

Series: The Physics of Compilation - Part 1 (Building Universes from Code) In the natural world, transition requires energy and time. A star does not simply "become" a supernova; it must undergo a profound, heavy conversion of elements at its core. It is a process of translation, where the invisible laws of nuclear physics manifest into a visible, physical reality. When we write code, we are working in the realm of human-readable abstraction. We use symbols, logic, and intent

Series: The Physics of the Undo - Part 3 (Building Universes from Code) If we were to record every single change in a complex digital universe, we would eventually run out of space. Even in a machine with gigabytes of memory, the "History Stack" is not infinite. We are forced to decide: How much of the past is worth saving? This brings us to the quiet engineering of State Management. We use snapshots, deltas, and circular buffers to manage the weight of history. We create a h

Series: The Physics of the Undo - Part 2 - Building Universes from Code When we ask a piece of software to "Undo," we aren't just asking it to "go back." We are asking it to manage a parallel history of everything that could have been. In engineering, this often leads us to the Command Pattern - an elegant, yet demanding structure where every action is packaged into a discrete object. A Command doesn't just execute an instruction; it stores the "memento" of what the world loo

The Physics of the Undo: Building Universes from Code In the physical universe, time moves in one direction. Entropy increases. A star that collapses cannot be un-collapsed; a glass that shatters on a stone floor does not spontaneously reassemble. The arrow of time is the ultimate, non-negotiable constraint of our existence. Yet, in the digital worlds we build, we have created a miracle that defies the very nature of reality: The Undo. We have cultivated a modern expectation

Series: When Humans Touch the System - Part 3 The final layer: Building trust that lasts In nature, resilience comes from systems that absorb variation without losing identity. Forests survive storms. Ecosystems adapt. Order persists, not because change is prevented, but because it is accounted for. Strong input validation does the same. It protects meaning over time. It ensures that as users come and go, as features evolve, as scale increases, the underlying structure remai

Series: When Humans Touch the System - Part 2 Validation isn't a gate; it's a blueprint for communication At first glance, validating input feels simple. Check the format. Reject what doesn’t fit. Move on. But the real world is never that tidy. Users bring context the system cannot see. They reuse fields in unexpected ways. They interpret labels differently. They enter values that are technically valid, but semantically wrong. And often, they do so consistently. This is what

Series: When Humans Touch the System - Part 1 Humans don't think in schemas - they think in possibilities In the natural world, structure emerges from countless individual actions. Snowflakes fall, grains of sand settle, rivers carve paths - none of them coordinated, yet together they shape landscapes that endure. User-created data works in much the same way. Every click, entry, upload, or choice a person makes feeds into a system. Each one feels small, harmless, obvious. But

Series: The Shape of Information - Part 3 The most important forces in the universe are invisible. We only notice them when something suddenly stops working. When data formats remain consistent, something remarkable happens. Systems become calmer. Integrations become predictable. Movement of information feels natural rather than forced. Importing data no longer feels like translation. Exporting no longer feels like explanation. Information moves through the ecosystem with its

Series: The Shape of Information - Part 2 Most data problems don’t arrive as disasters. They arrive quietly - field by field, assumption by assumption - until trust in the system begins to fade. In nature, erosion rarely happens all at once. A coastline doesn’t vanish overnight. It changes grain by grain, tide by tide, until the landscape no longer resembles what it once was. Data inconsistency behaves the same way. A field is renamed here. A unit is interpreted differently t

Series: The Shape of Information Nothing in the universe moves without shared rules. Light, matter, energy - all travel because the structure they pass through is understood. Software is no different. In the natural universe, communication follows rules. Light travels in waves that can be measured. Matter behaves according to predictable laws. Even chaos has structure, if you look closely enough. Without these shared rules, nothing could interact. Nothing could persist. Softw

Rivendell Isn’t Where You Give the Burden Away The others didn’t arrive because I asked them to carry the story for me. They came because I needed it to be seen. Up until now, this had been a narrow road. A handful of companions. A weight carried quietly, carefully, so it didn’t trouble anyone else. But if the story was going to be done properly, not rushed, not broken, not shaped by fear, then it couldn’t stay private anymore. So I let people in. Not to fix it. Not to lead i

Series: Performance as a Law of Nature - Part 3 In nature, stability does not come from rigidity. It comes from balance. Trees bend with the wind. Rivers adjust their course. Living systems survive not because they are fastest, but because they respond gracefully to change. When software is designed with performance in mind from the beginning, it begins to behave in the same way. Instead of piling on complexity, we simplify. Instead of assuming abundance, we respect limits. I

Series: Performance as a Law of Nature - Part 2 In theory, we imagine systems as clean and orderly - like perfect equations written on a page. But the natural world is never that simple. Weather shifts. Surfaces erode. Forces interact in ways that are subtle, cumulative, and often invisible until something gives way. Software behaves much the same. What feels smooth in isolation can struggle when exposed to real conditions. Different patterns of use. Different moments of dema

Series: Performance as a Law of Nature - Part 1 In the natural world, everything moves at its own necessary speed. Light crosses vast distances without hesitation. Rivers flow without pausing to consider the rocks in their path. Seasons change not when it is convenient, but when the conditions demand it. The universe does not wait. When we build software, it is easy to forget this. Inside our tools, time feels flexible. Delays are tolerated. Systems pause politely while we th

The Morning After I woke up and, for the first time in a long while, there was no sense of danger. Nothing watching. Nothing chasing. Nothing waiting for me to fail. Just warmth. Stillness. That deep, unfamiliar feeling of being properly looked after. Rivendell has a way of doing that. It doesn’t demand anything from you. It simply lets you rest until you remember who you are again. When I stepped outside, the others are there. Merry/Pippin, being exactly like they are, laugh

Series: Seamless Worlds - Part 3 When seamless transitions are automated, something profound changes. Creators stop thinking in terms of levels and start thinking in terms of places. They design journeys, not hand-offs. Moments, not mechanisms. The engine takes responsibility for continuity - deciding what persists, what streams, what fades, and what emerges - all without requiring the creator to intervene. The world becomes a single, flowing structure rather than a sequence

The Stand There is a point where you can’t outrun the doubt anymore. The climb to the river was the hardest part. Quiet. Heavy. It was the kind of stretch where the Dark Riders don’t even need to shout; they just wait for you to run out of breath. I reached the water with nothing left. No clever turns. No narrative tricks. Just the deep realization that I was ready to let the shadows have it. The Protector at the Water's Edge But my Arwen was there. My Arwen doesn’t write the

Series: Seamless Worlds - Part 2 Behind every seamless transition lies a careful balancing act. Assets must be loaded without disrupting performance. State must be preserved without duplication or loss. Systems must agree on what carries forward - and what must be left behind. Characters, physics, audio, AI, narrative triggers - all of them must survive the crossing intact. The difficulty is not just technical, but architectural. If each system handles transitions differently

Series: Seamless Worlds - Part 1 In the natural universe, there are no loading screens. You don’t step from one place to another and feel reality pause. Space flows continuously. Time never stutters. The universe does not announce that you’ve crossed a boundary - it simply carries on. Game worlds, by contrast, are divided. Levels end. New ones begin. Memory is unloaded. Assets are rebuilt. And if this transition is handled poorly, the illusion breaks. The player is reminded -

I don’t need much. Just one warm intro that actually replies and a roadmap that survives contact with reality. I've already got a team that believes, so I’m not asking for miracles. And maybe, one night of sleep without LinkedIn notifications. Milk and cookies will be left out. Along with a cap table and a pitch deck, just in case you know anyone who might be interested. From a founder who still believes great things start simple. John Thornewill 22nd December 2025