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 really like your videos on architecture. They are simple, yet with enough detail to convey meaningful information. So thank you for taking the time to create these videos. As an aside, I must say that us devs really like naming things to make things sound so much more complex than they are... "Inverse Conway Manouvre"?! Whoever came up with this had way too much time on their hands.
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.
@@cuicuidev Casey explicitly describes Conway's law as "The Only Unbreakable Law" in the video title (but he admit's that you can't be 100% sure yet it's a law), and also draws the parallel to it being a law like Newton's law of gravity: a law that will remain true, except in very specific scenarios where an updated law must be used (like Einstein's relativity theory). Also this is an excellent video, I came here from Casey's video and the relation of Conway's law with layered and cross-functional teams is very interesting.
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 ❤
I really like your videos on architecture. They are simple, yet with enough detail to convey meaningful information. So thank you for taking the time to create these videos.
As an aside, I must say that us devs really like naming things to make things sound so much more complex than they are... "Inverse Conway Manouvre"?! Whoever came up with this had way too much time on their hands.
Thanks! I'm glad you like the videos.
I totally agree. Another good one is "Anti-Corruption Layer" - why on earth did they call it that?!
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
Wondeful video as always! Eager for the next one
Thanks very much :) Next one is in progress!
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
Thanks!
“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...
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.
@@cuicuidev Casey explicitly describes Conway's law as "The Only Unbreakable Law" in the video title (but he admit's that you can't be 100% sure yet it's a law), and also draws the parallel to it being a law like Newton's law of gravity: a law that will remain true, except in very specific scenarios where an updated law must be used (like Einstein's relativity theory).
Also this is an excellent video, I came here from Casey's video and the relation of Conway's law with layered and cross-functional teams is very interesting.