Economics is where I spent my actual undergraduate studies, and I worked as a fintech data analyst and engineer in the early years of my career. While I work professionally as a more general software engineer and project manager at this point, I still like to keep up with more econometrics and policy-focused topics.
When I was studying economics, most of my academic focus was in market design and non-monetary systems like:
— To understand why OpenAI completely upended the world of mathematics with its proof that Navier-Stokes is not smooth in three dimensions, you must first understand that cucumbers of any size can be properly pickled.
— I think I’ve found a pretty large CVE that has gone without a formal report, despite absolutely saturating the field of software engineering. It’s subtle and…
— Many an engineer has heard tales of Valve's "flat" organization structure — what is fact, what is fiction, and how does it actually work? An annotated copy of the 2012 First Edition of Valve's Employee Handbook.
— Our lives are all dominated by a little graph in our hearts — and sometimes, that graph gets wacky. A review of Dietrich Bonhoeffer's "Theory of Stupidity", part of his larger ~1943-1945 work "Letters and Papers from Prison."
— Do humans have a role in software development anymore? Absolutely — but we need to rethink what it means to program. An modern review of Peter Naur's 1985 essay "Programming as Theory Building"
— How dense is too dense? How sparse is too sparse? Annotations for A Pattern Language's proposals for the density of metro-adjacent country streets for agriculture, recreation, and preservation.
— Home isn't where the heart is — it's a single node on a very, very large graph. Annotations for the "Independent Regions" pattern of *A Pattern Language*.
— How close is too close? How far is too far? *A Pattern Language* annotations related to the statistical, economic, and ecologic concerns in balancing how dense human habitats ought to be.
— City, with natural stripes — or nature, with city stripes? Annotations for A Pattern Language, and tracking public opinion of where Americans want to live over the past 50 years.
— The beginning of a topological review of the 1977 urban design and architecture reference book A Pattern Language, and a journey to understand Earth's greatest graph: the Earth, itself.
— Annotations for Greiner's 1972 paper "Evolution and Revolution as Organizations Grow", about the structural composition of organizations at different sizes and requirements.
— My time at the University of Utah was longer than I'd planned, cut shorter than expected by COVID-19.
I was very lucky to have mentorship to push me across the finish line.
— Stop reprocessing your entire dataset every time new data arrives.
A practical guide to Spark Structured Streaming with code examples and cost logic.
— Efficiency: spending six hours building a web scraper to avoid five minutes of daily work.
Automating a business simulation because checking in is for chumps.
— My college presentation on the Gale-Shapley paper, recorded on an iPad, like a true professional.
Non-market environments, matchmaking lattices, and gratitude for good professors.
— A first foray into network visualization: messy graphs, abject terror.
Early data viz experiments searching for supply loops. Bad graphs; interesting questions.
— Do humans have a role in software development anymore? Absolutely — but we need to rethink what it means to program. An modern review of Peter Naur's 1985 essay "Programming as Theory Building"
— Home isn't where the heart is — it's a single node on a very, very large graph. Annotations for the "Independent Regions" pattern of *A Pattern Language*.
— My time at the University of Utah was longer than I'd planned, cut shorter than expected by COVID-19.
I was very lucky to have mentorship to push me across the finish line.
— How close is too close? How far is too far? *A Pattern Language* annotations related to the statistical, economic, and ecologic concerns in balancing how dense human habitats ought to be.
— Stop reprocessing your entire dataset every time new data arrives.
A practical guide to Spark Structured Streaming with code examples and cost logic.
— To understand why OpenAI completely upended the world of mathematics with its proof that Navier-Stokes is not smooth in three dimensions, you must first understand that cucumbers of any size can be properly pickled.
— City, with natural stripes — or nature, with city stripes? Annotations for A Pattern Language, and tracking public opinion of where Americans want to live over the past 50 years.
— The beginning of a topological review of the 1977 urban design and architecture reference book A Pattern Language, and a journey to understand Earth's greatest graph: the Earth, itself.
— Annotations for Greiner's 1972 paper "Evolution and Revolution as Organizations Grow", about the structural composition of organizations at different sizes and requirements.
— My college presentation on the Gale-Shapley paper, recorded on an iPad, like a true professional.
Non-market environments, matchmaking lattices, and gratitude for good professors.
— I think I’ve found a pretty large CVE that has gone without a formal report, despite absolutely saturating the field of software engineering. It’s subtle and…
— Many an engineer has heard tales of Valve's "flat" organization structure — what is fact, what is fiction, and how does it actually work? An annotated copy of the 2012 First Edition of Valve's Employee Handbook.
— How dense is too dense? How sparse is too sparse? Annotations for A Pattern Language's proposals for the density of metro-adjacent country streets for agriculture, recreation, and preservation.
— Efficiency: spending six hours building a web scraper to avoid five minutes of daily work.
Automating a business simulation because checking in is for chumps.