<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>systems-thinking on Aban Hasan</title><link>https://www.abanhasan.net/tags/systems-thinking/</link><description>Recent content in systems-thinking on Aban Hasan</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 09 Oct 2025 17:45:27 +0530</lastBuildDate><atom:link href="https://www.abanhasan.net/tags/systems-thinking/index.xml" rel="self" type="application/rss+xml"/><item><title>The Asymmetry of Asynchrony</title><link>https://www.abanhasan.net/posts/the-asymmetry-of-asynchrony/</link><pubDate>Thu, 09 Oct 2025 17:45:27 +0530</pubDate><guid>https://www.abanhasan.net/posts/the-asymmetry-of-asynchrony/</guid><description>One of my favorite programming paradigms is asynchrony, and it has profound analogues in our complex modern world. We take it for granted that we can request a service, let it run in the background, and receive results in a reasonable amount of time. This was one of the great transformative processes of our 21st century world, something technologically infeasible before the rise of the telephone.
Modern systems are designed to never wait.</description></item></channel></rss>