I just stumbled on this after writing an abstract on societal structures with an outlook on how to construct them in the first place. This is great food for thought as it also applies to forming governmental bodies/institutions. Thanks a lot, may the views be with you!
Thanks! Melvin Conway noted that the idea has "much broader utility" than just software engineering. He even mentions governments specifically. Worth checking out www.melconway.com/Home/Committees_Paper.html
I was once in a project where I was forced to implement an architecture that is totally different to the team structure. it was a nightmare while the startup founder CTO lives in his ivory tower
“Ok everyone organize yourself into lambda calculus structure. No killing/eating of each other when iterating. No, Tommy, you’re not going to be the universally inhabited type in calculus of inductive constructions, again.”
"Great job everyone, now our Loop Enablement Team have built the YCombinatorService so other teams don't have to worry about the complexity of recursion". What could possibly go wrong...
Thanks! It's "law" like in "Moore's Law", "Murphy's Law", or "Newton's First Law". Like a law of nature. It's just an observation of a thing that happens. Personally I like how that differentiates it from a "pattern" or "practice" that you can chose to follow or ignore.
@@drawingboxes I'm not sure I could explain myself clearly on this, as I'm not a native english speaker, but there's a pretty good talk on RUclips by Casey Muratori on the same topic that aligns with my point of view (and it somewhat influenced me). If you're interested, just type his name and Conway's law.
Again; great explanation; Now I understand why big company divide teams like that;
I just stumbled on this after writing an abstract on societal structures with an outlook on how to construct them in the first place. This is great food for thought as it also applies to forming governmental bodies/institutions. Thanks a lot, may the views be with you!
Thanks! Melvin Conway noted that the idea has "much broader utility" than just software engineering. He even mentions governments specifically. Worth checking out www.melconway.com/Home/Committees_Paper.html
@@drawingboxes Thanks a bunch! I will definitely check that out ❤
Wondeful video as always! Eager for the next one
Thanks very much :) Next one is in progress!
You definitely have a talent! Another great video to use in class :)
Thank you! Glad to hear you're getting good use from these videos
I was once in a project where I was forced to implement an architecture that is totally different to the team structure. it was a nightmare while the startup founder CTO lives in his ivory tower
“Ok everyone organize yourself into lambda calculus structure. No killing/eating of each other when iterating. No, Tommy, you’re not going to be the universally inhabited type in calculus of inductive constructions, again.”
"Great job everyone, now our Loop Enablement Team have built the YCombinatorService so other teams don't have to worry about the complexity of recursion". What could possibly go wrong...
Thanks!
Nice!
Great explaination! Although this behaviour hardly qualifies as a law imo
Thanks! It's "law" like in "Moore's Law", "Murphy's Law", or "Newton's First Law". Like a law of nature. It's just an observation of a thing that happens. Personally I like how that differentiates it from a "pattern" or "practice" that you can chose to follow or ignore.
@@drawingboxes I'm not sure I could explain myself clearly on this, as I'm not a native english speaker, but there's a pretty good talk on RUclips by Casey Muratori on the same topic that aligns with my point of view (and it somewhat influenced me). If you're interested, just type his name and Conway's law.