@ryanlpeterman: The only unbreakable law in software engineering ⠀ Casey Muratori (Video Game Dev & Creator): What is the only unbreakable law in software engineering? The only thing I've seen that feels like a real law to me is the thing I cover in this lecture, which is Conway's law. ⠀ And it is that if you would like to organize a series, like a set of people to work on something, or in the modern parlance, let's say agents, if you need to partition a problem into a set of workers in this way where the communication between those workers is slower than their own internal computation ability, when you start to tackle a problem, in order to get the benefits of that parallelization, you will have to make decisions about who is working on what. ⠀ Once you've made that decision, you have now locked in the fact that that the iteration on the design will be slower across that boundary than it is interior to either of the two parts. One way the rule is pithily stated is products look like the org chart, right? ⠀ But that's not exactly what it says. But that's a downstream consequence and boy do you ever see it in the real world. ⠀ For the full conversation, you can search Casey Muratori on my YouTube, Spotify or Apple Podcasts (link in bio)
Ryan Peterman
Region: US
Thursday 17 September 2026 13:06:55 GMT
Music
Download
Comments
andrewships :
Most unnecessarily confusing explanation of conways law 😅
2026-09-17 15:37:12
1182
Jhered Parnell :
I've literally never heard a more complex explanation of Conway's law. the way you organize people influences the architecture of the software
2026-09-17 17:04:51
371
DELU. :
There is only ONE universal law in development:
You don't ship on Fridays...
2026-09-17 16:13:40
448
LiteUpJack :
that's literally the most wordy way to describe Conway's law
2026-10-29 06:15:34
0
Neo :
Conway’s law: Organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations.
2026-09-17 17:39:49
186
zzopd :
Adding more software engineers doesn’t scale development speed linearly because every person you add also adds communication and coordination overhead. Delegating work means designs, interfaces, and assumptions have to be communicated and kept synchronized instead of simply changed in one person’s head. As the team grows, more effort goes into coordination, so the efficiency gained from additional workers gradually gets eaten away by the cost of keeping everyone aligned.
2026-09-17 17:00:08
48
user3141592653587932384 :
Most complicated way to say “different people do the same thing differently, if they dont talk to each other about it with each other”
2026-09-17 20:31:33
36
SapGuy77 :
You can't divide by zero. Ever.
2026-09-18 10:28:35
6
儿 :
i prefer the podcast law: anyone on a podcast will somehow produce the most convoluted explanation of the simplest topic
2026-09-18 06:35:55
8
Alex :
NEVER release on a Friday!
2026-09-17 19:41:48
18
Bumblebeetuna :
The Golden Rule: Never deploy to production on a Friday unless it’s to fix something that’s broken.
2026-09-18 02:57:31
11
Darrin - Enlightened_D :
Bro get to the point
2026-09-17 17:53:46
35
Stefan Lats :
“Fix it now Claude, no mistakes, best code, best practice, no security gap, optimised, make me rich, very rich” - isn’t that it
2026-09-18 13:22:00
5
allezz_juve :
that is the most confusing description to be honest
2026-09-17 21:53:33
11
Michael :
Otherwise stated, it’s slower to talk to and work with other teams to create services that address cross-cutting concerns than it is to create services, however inefficient the architecture is, that only have one team owner
2026-09-17 13:19:39
33
l.gamezp :
what an unnecessarily complicated answer
2026-09-17 18:13:23
31
Dgcaste :
The assumption here is that speed matters. Although speed can matter, it doesn’t always matter. The focus of how structure the solution path should instead be on quality of output for the end user and for the org itself.
2026-09-17 15:21:26
8
aloneinafog :
Wrong answer. Never commit your .env files. That’s it
2026-09-17 15:43:42
15
JGS :
thats such a long way of saying "the architecture will mirror the org chart"
which I 100% agree with btw
2026-09-17 15:06:41
25
alexasiricortanay :
Brooks Law
2026-09-18 05:43:02
0
Hamid Ebadi :
this guy is purposely confusing or what?
2026-09-18 06:01:05
2
Rick :
This is not a software problem
2026-09-17 16:54:40
1
Chuckles :
I’m and engineer and this is the most complicated way of explaining Conway’s Law
2026-09-17 19:52:05
4
kenneyaf :
This is why the design should always be final. I don’t care how archaic that idea is, it increases quality. If the design *must* change during development, then the problem is changing parallel to the solution and will never be final.
2026-09-21 20:43:05
0
robgibson23 :
I'm a lawyer and I've seen tax code more clear than this explanation.
2026-09-18 07:04:58
1
To see more videos from user @ryanlpeterman, please go to the Tikwm
homepage.