// thinking
Interests
These three things look different on the surface. They're not. Each one is a version of the same question: how do complex systems with many interacting parts produce outcomes that feel, in retrospect, inevitable? That question is what makes me care about database schema design, LLM pipeline architecture, and why the Roman Empire fragmented along the exact lines it did.
Empires & Civilizations
The interesting question isn't what happened — it's why it had to happen that way. Geography determines agricultural surplus. Surplus determines population density. Density determines military capacity. Capacity determines which states form, which expand, and which collapse under their own administrative weight.
The cases that break that chain are the most interesting. Where does contingency actually override structural determinism? Why does geography keep producing the same strategic chokepoints across unrelated civilizations centuries apart? Why do empires tend to fragment along the same cultural and geographic fault lines they spent decades trying to paper over?
The pattern that keeps appearing: the same forces that enable a system to scale are usually the ones that make it brittle at scale. True for Rome. True for software.
Game Design & TTRPGs
The design challenge is producing emergent complexity from simple primitives — rules a player can hold in their head that generate decisions they couldn't predict in advance. A good ruleset has a small surface area and a large possibility space. A bad one has exceptions layered on exceptions until the system is only legible to the person who wrote it.
The same constraint applies to software interfaces. An API that requires reading 40 pages of documentation to use correctly has the same design failure as a rulebook that needs a GM ruling every 10 minutes. Complexity should emerge from composition, not accumulation.
I've built a custom TTRPG system from scratch and a long-form D&D campaign with faction systems designed to act on independent motivations rather than react to players.
Worldbuilding & Fiction
A world has to make sense from first principles. If the geography is wrong, the economics are wrong. If the economics are wrong, the political systems are wrong. If the political systems are wrong, the culture is wrong. Aesthetic choices come last — they're downstream of the causal structure, not a substitute for it.
Internal consistency matters more than novelty. A world that follows its own rules rigorously will surprise you in ways that feel earned. A world built backward from the story the author wanted to tell will have seams everywhere.
I've been building Avalor using QGIS and geospatial modeling — tectonic plates first, then climate, then hydrology, then biomes, then civilizations. The same instinct that makes me care about why rivers go where they do is the one that makes me care about why a database schema should be structured a certain way.