Organizations design systems that mirror their own communication structure.
Laws of Software Engineering
A collection of principles and patterns that shape software systems, teams, and decisions.
Systems design 3: LLMs and the semantic revolution
Long ago in the 1990s when I was in high school, my chemistry+physics teacher pulled me aside. "Avery, you know how the Internet works, righ...
You can't design software you don't work on
Only the engineers who work on a large software system can meaningfully participate in the design process. That’s because you cannot do good software design without an intimate understanding of the concrete details of the system. In other words, generic software design advice is typically useless for most practical software design problems.
Atomic Design by Brad Frost
Learn how to create and maintain digital design systems, allowing your team to roll out higher quality, more consistent UIs faster than ever before.
Software Should Be Allowed to Be Weird - Ewan’s Blog
A fairly large amount of the software I write would probably die in a corporate planning meeting. There would be questions about the target audience, the bu…
All you need is links
When Tim Berners Lee talks about how he designed the web, he uses an analogy from physics, describing his process as a quest to find “fundamental laws” which can generate a desired system:
Harness engineering: leveraging Codex in an agent-first world
By Ryan Lopopolo, Member of the Technical Staff
Design for a Living Planet: Settlement, Science, & the Human Future
In this brief, accessible volume, the authors — an urban philosopher and a mathematician-physicist — explain the surprising new findings from the sciences that are beginning to transform environmental design in the modern era. Authors Michael Mehaffy and Nikos Salingaros explore fractals, networks, self-organization, dynamical systems and other revolutionary ideas, describing them to non-science readers in a direct and engaging way. The book also examines fascinating new topics of design, including Agile, Wiki, Design Patterns and other “open-source” approaches from the software world. The authors conclude that a profound transformation is under way in modern design — and today’s students and practitioners will need to be aware of its implications for our future.“Lucidly describes what’s coming in the world of design — and what needs to come.” — Ward Cunningham, Inventor of wiki, and pioneer of Pattern Languages of Programming, Agile, and Scrum“Essential reading for all urban designers.” — Jeff Speck, Author of Walkable City“Brilliant.” — Charles Montgomery, Author of Happy City“Inspired, compelling and fascinating… Recognizes that a true architecture can be dug from the facts, insights, and theories, that occur with a broadening of science to include the human being.” — Christopher Alexander, Author of A Pattern Language and Notes on the Synthesis of FormSome comments on the individual chapters:“Packed with detail and beautiful in presentation.” — Gil Friend“Human society must find a path of retreat. Salingaros and Mehaffy point the way.” — David Brussat, Providence Journal“Michael Mehaffy and Nikos Salingaros have written some brilliant articles on how we can co-create cities which are truly resilient, rather than being ‘engineered resilient’.” — Smallworld Urbanism“For me, this essay was like a flash of insight, and I suddenly saw the world in a new light.” — Oeyvind Holmstad, Permaliv“We’ve just come across a very thoughtful article by Michael Mehaffy and Nikos Salingaros… [who] draw a number of lessons from biological systems and use them to draw conclusions about how resilient human systems must be designed.” — Resilient Design Institute“Salingaros and Mehaffy take us from the configuration of city spaces to the order of cells in living beings.” — Jaap Dawson, Delft Institute of Technology“If you wanted to know where the cutting edge was in urban design, it is here.” — Patrick J. Kennedy, CarFreeInBigD“This is the single most intelligent and illuminating article I’ve seen on Archdaily in 3 years.” — Nìming Pínglùn Zhě, ChinaMichael Mehaffy is an urbanist and design theorist, and a periodic visiting professor or adjunct in five graduate universities in four countries and three disciplines (architecture, urban planning and philosophy) including the University of Oregon (US) and the University of Strathclyde (UK). He has been a close associate of the architect and software pioneer Christopher Alexander, and a Research Associate with the Center for Environmental Structure, Alexander’s research center founded in 1967. He is currently executive director of Portland, Oregon based Sustasis Foundation, and editor of Sustasis Press.Nikos A. Salingaros is a mathematician and polymath known for his work on urban theory, architectural theory, complexity theory, and design philosophy. He has been a close collaborator of the architect and computer software pioneer Christopher Alexander. Salingaros published substantive research on Algebras, Mathematical Physics, Electromagnetic Fields, and Thermonuclear Fusion before turning his attention to Architecture and Urbanism. He is Professor of Mathematics at the University of Texas at San Antonio and has been on the Architecture faculties of universities in Italy, Mexico, and The Netherlands.
Programming (with AI agents) as theory building
Back in 1985, computer scientist Peter Naur wrote “Programming as Theory Building”. According to Naur - and I agree with him - the core output of software engineers is not the program itself, but the theory of how the program works. In other words, the knowledge inside the engineer’s mind is the primary artifact of engineering work, and the actual software is merely a by-product of that.
What Functional Programmers Get Wrong About Systems - Ian Duncan
Type systems verify properties of programs. Production correctness is a property of systems. The gap between these is where the interesting failures live.
Coding After Coders: The End of Computer Programming as We Know It - …
archived 16 Mar 2026 15:14:04 UTC
Tests Are The New Moat | Daniel Saewitz
As AI becomes better at cloning people's open source work, what ends up becoming most valuable are software contracts, tests, and API surface area. This clashes the incentives of clearly defining your commercialized open source software with protecting it.
Requisite variety and its implications for the control of complex systems
Recent work on the fundamental processes of regulation in biology (Ashby, 1956) has shown the importance of a certain quantitative relation called the law of requisite variety. After this relation had been found, we appreciated that it was related to a theorem in a world far removed from the biological—that of Shannon on the quantity of noise or error that could be removed through a correction-channel (Shannon and Weaver, 1949; theorem 10). In this paper I propose to show the relationship between the two theorems, and to indicate something of their implications for regulation, in the cybernetic sense, when the system to be regulated is extremely complex. Since the law of requisite variety uses concepts more primitive than those used by entropy, I will start by giving an account of that law.
Clan 2025 Wrap-Up: From Infrastructure to a New Computing Paradigm
A look back at what we built in 2025 and where Clan is heading next
Software Acceleration and Desynchronization
A look at the ever-present drive to make software delivery faster and how it might break down various activity loops in organizations.
