How I Finally Stopped Worrying & Learnt to Love Conway’s Law • James Lewis • GOTO 2015

This presentation was recorded at GOTO Chicago 2015
gotochgo.com
James Lewis - Principal Consultant at ThoughtWorks
ABSTRACT
Go faster than your competitors. That's the promise of microservices - deploy faster, scale faster, be more robust. It's all about outcomes and the way your organisation is structured has a tremendous impact on those outcomes. it’s easy to say “Conway’s Law” and [...]
Download slides and read the full abstract here:
gotocon.com/chi...
/ gotochgo
/ gotoconference
gotocon.com
#ConwaysLaw #Conway #Microservices
Looking for a unique learning experience?
Attend the next GOTO conference near you! Get your ticket at gotopia.tech
Sign up for updates and specials at gotopia.tech/n...

[@MatthewChaplain]

What I learned from this very interesting talk is that no-one wants to communicate with HR.

[@HaroldCombs]

Matthew Chaplain what makes you say that?

[@MatthewChaplain]

Harold Combs 8:55 and 27:42

[@completelynoname2065]

Connecting Dunbar's number to software architecture and Conway's law was the most important insight for me here. Thanks.

[@philipoakley5498]

The distance v weekly communication graph is interesting in the modern post COVID work from home (WFH) discussions.

[@Kratax]

Good information, but the presentation could have had better structure and form. Also some parts were missing, for example I would have added documentation and elaborated more on how to enforce software architecture and customer service model.

[@ianrogers7543]

That was pretty vacuous. The quotes from other people were useful, but James' contributions were platitudes or strawman sniping - and the punchline at the end contradicted the Statler posturing he used all the way through the previous 40 minutes. tl;dr - Conway was right, set up your company to communicate the right way and the architecture will follow.

[@JeremyAndersonBoise]

Ian Rogers jeez golly I guess you have it all figured out. Good luck with that.