







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…
You have to know how to drive the car
There are lots of different ways to be a software engineer. You can grind out code for twelve hours a day to make the world a better place. You can focus on glue work: process-based work that makes everyone around you more successful. You can join the conversation with your product manager and designer colleagues to influence what gets built, not just how it gets built. You can climb the ladder to staff engineer and above, or you can take it easy and focus on your hobbies. But whichever of these you choose, you have to know how tech companies work.

Conway's Law | Laws of Software Engineering
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.

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.

The Future of Software Engineering Isn’t What You Think
Over the past two decades, I’ve watched software eat the world, then hardware catch up, then Generative AI reshape both at the same time…
Why Can’t Programmers... Program?
I was incredulous when I read this observation from Reginald Braithwaite: Like me, the author is having trouble with the fact that 199 out of 200 applicants for every programming job can’t write code at all. I repeat: they can’t write any code whatsoever. The author he’s
You have to beat the models at something
In 2025, I wrote that software engineers ought to be assessed by “value over replacement”: not how much money they made for their company, but how much they…
“This Is Not The Computer For You” · Sam Henri Gold
Sam Henri Gold is a product design engineer building playful, useful software.

Large tech companies don't need heroes
Large tech companies operate via systems. What that means is that the main outcomes - up to and including the overall success or failure of the company - are driven by a complex network of processes and incentives. These systems are outside the control of any particular person. Like the parts of a large codebase, they have accumulated and co-evolved over time, instead of being designed from scratch.

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…
Impeccable: Design skills for AI harnesses
1 skill, 23 commands, and curated anti-patterns for impeccable frontend design. Works with Cursor, Claude Code, GitHub Copilot, Gemini CLI, and Codex CLI.

Impeccable: Design skills for AI harnesses
1 skill, 23 commands, and curated anti-patterns for impeccable frontend design. Works with Cursor, Claude Code, GitHub Copilot, Gemini CLI, and Codex CLI.

A practical guide to frontend System Design
Sam, a passionate frontend developer, had been in the job market for what felt like...

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.

Making the Case for Actionable Prosocial Design Research
Regulating harmful design is only half the equation — attention must also go toward how platforms can build prosocial design, and toward the research that shows them how.

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.