Podcasts about conway's law

Matt and Ben compare monorepo vs multi-repo layouts, explain Conways Law, talk about what a 'team' is, and what Visual Source Safe isn't. Ben defines how big a service should be. Matt recalls a brief interlude with Clojure.

Conway's Law wurde bereits im Jahre 1968 ausgestellt, doch bietet bis heute Aktualität und einen guten Ansatz sich über bestehende Strukturen Gedanken zu machen. Kurz gesagt, Kommunuikations- und Organisationsstrukturen bilden nehmen Einfluss auf das zu entwickelnde Produkt und deswegen macht es mehr Sinn Strukturen entsprechend der Vorgaben des Produktes zu entwerfen. Dein Gedankenhappen: "Erst zusammenwachsen, dann zusammen wachsen."

Data on Kubernetes #7: Conway's Law & Kubernetes - Centralization vs small team autonomy with Mike Tougeron, Lead Site Reliability Engineer, at Adobe & Joseph Sandoval , SRE Manager, Platform Infrastructure, at Adobe. Loosely coupled teams, loosely coupled workloads and loosely coupled data - on a built for everyone platform? Abstract: Big clusters or small clusters? Where to draw the line and how to know whats best for your use case? We speak with Joseph and Mike from Adobe about the inevitable questions that arise when running k8s at scale. If it is run by the platform team, is it inevitably a pet? Or more of a pet? Is that the idea, that we give stuff that ” must not fail” to platform teams so they are common services w/ SLAs? Or how is it decided what is owned by the platform vs. the individual teams. While talking with Joseph and Mike we also dive into what their stack looks like, must have tools they use on a daily bases, VM vs K8s, differences in stateful apps on k8s and War stories! Mike T Bio: For many years Mike has been building Kubernetes platforms and deployments. With a passion for automation and developer engagement, Mike works towards continuously improving development pipelines to take the complication out of managing services on large-scale infrastructure backed by both vm and containers across multi-cloud environments. Mike is a lazy programmer who would rather write thousands of lines of code for automation instead of running repetitive commands every day. When not coding or playing with his son you'll find Mike with his nose buried in a book or playing Civilization. Joseph Sandoval Bio: Joseph has been in the tech industry for 25 years running large scale infrastructure primarily in the E-commerce/SaaS. The last 15 years has been spent in leading and a managing role with the high performing. His philosophy is to create space for SRE's to do their best work and espousing a product centric point of view when it comes to backend infrastructure and tooling. Currently managing a team responsible for over 200k cores of infrastructure (bare metal, vm's and containers) in 6 datacenters and 3 AWS regions. ▬▬▬▬▬▬ Connect with us

Christian Nilsson, Global Head of Advisory at Cloudreach, joins the team today to discuss how Conway's Law applies to cloud adoption. Referring to the law, Christian suggests that systems reflect organizations and vice versa, supporting the notion that focusing on people, rather than tech, is a far more effective way of delivering transformation. Ultimately, adopting cloud is a chance to review your principles and operating model, not just how your applications are powered.

Microservis mimarisi, SOA, DevOps gibi kavramların temelinde, çekirdeğinde yer alan Conway'in yasası, sektörde hiçbir zaman gereken ilgiyi görmedi. Geliştirdiğiniz ürünün yapısı ve tasarımı nasıl olurda ekip içi ve ekipler arası iletişim kanallarının sayısı, şekli ve yapısı ile ilişkili olur, hiç sormadık. Bu nedenle devops ve agile dönüşümlerde hep bir yerler eksik, bir yerler sorunlu kaldı. Biz de bu uzun podcastimizde, çoğunlukla sadece bir cümle ile telaffuz edilip geçilen bu ilham verici fikir üzerine derinlemesine konuşmak istedik.

This week we spoke with Chip Childers, technology chief of staff at the Cloud Foundry Foundation, about the technical and architectural decisions that help define the modern enterprise. Cloud Foundry Foundation is the independent organization that oversees the development and adoption of the Cloud Foundry platform, and it's a sponsor of The New Stack. More than half of the Fortune 500 uses Cloud Foundry, so the Cloud Foundry Foundation depends on the enterprise using, contributing to, and advancing its open source projects. Childers works closely with developers and CIOs at all of the foundation's member companies, and so he has a deep understanding of what it is that a modern enterprise needs in order to succeed in today's rapidly changing technology landscape. In a recent post for The New Stack, he wrote that  “Modern enterprises ... think critically about what they should build themselves and what they should source from somewhere else.”

They discuss how to pronounce The Bombe, Adam talks about Conway's Law, and Safia compares sexism in the workplace to warfare.

CEO and Co-Founder Andrea Goulet of the tech-debt fixing company, https://corgibytes.com stops by the People Stack to talk about building a community of Menders (https://www.legacycode.rocks/), knowing when and when your org needs Menders vs Makers, the Org Smells that show dysfunction in your org, how Conway's law impacts your tech debt and more. The book Andrea refers to in this episode is "The Five Dysfunctions of a Team: A Leadership Fable" by Patrick M. Lencioni. Here is an Amazon link to it: https://www.amazon.com/Five-Dysfunctions-Team-Leadership-Lencioni-ebook/dp/B006960LQW Intro music is "I'm Going for a Coffee" (http://freemusicarchive.org/music/Lee_Rosevere/Music_For_Podcasts_3/02_Im_Going_for_a_Coffee) by Lee Rosevere, which is licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Special Guest: Andrea Goulet.

In this episode, we chat with Adam Tornhill. Adam is the author of Your Code as a Crime Scene as well as Software Design X-Rays: Fix Technical Debt with Behavioral Code Analysis. He’s also the founder of Empear, whose flagship product, CodeScene, helps companies prioritize technical debt by identifying “hotspots” within their codebases.  During the show we talk about:  How Adam's background in psychology informs his work as a software developer.  Different ways to measure complexity Using behavioral analysis and Conway's Law to help prioritize areas to work on in your code.  We hope you enjoy! Be sure to check out https://legacycode.rocks for even more great conversations about modernizing software. 

Als Revisor fällt es nicht leicht, folgende Punkte als valide zu betrachten und als Ausgangspunkt einer Prüfung zu nehmen: - Menschen und ihre Interaktionen sind wichtiger als Prozesse und Werkzeuge - Funktionierende Software ist wichtiger als umfassende Dokumentation - Zusammenarbeit mit dem Kunden ist wichtiger als Vertragsverhandlungen - Eingehen auf Veränderungen ist wichtiger als Planerfüllung Ist dieses Agile Manifest tatsächlich ein rotes Tuch für Revisoren? Was ist das Geheimnis hinter SCRUM? Welche Erfolgsfaktoren stecken dahinter? Lassen sich SCRUM-Projekte von einem Außenstehenden sinnvoll prüfen? Falls ja, wie könnte man sinnvoll vorgehen? Diesen Fragen gehe ich in diesem Interview mit dem SCRUM-Experten Sylvius Gerber nach. Lassen Sie sich überraschen von seiner Einschätzung. Mittendrin streifen wir dann auch Conway's Law, welches ich hier verlinke: https://de.wikipedia.org/wiki/Gesetz_von_Conway Wer die Agile Sprechstunde von Sylvius Gerber nutzen möchte, kann sich über seine webpage www.veraenderungskraft.de dafür anmelden. Viel Spaß beim Anhören und erfolgreiche Prüfungsprozesse!

Metaphors may seem like a literary device that has no relevance in software, but nothing could be further from the truth. On today's episode, we dive deep into the world of explaining the abstract with Nat Pryce. We touch on George Lakoff, Conway's Law, Lehman's Laws, the difference between cognitive and figurative metaphors, and much, much more. If you've ever wanted to learn how to explain your work better, especially to people who don't code very much, this is one episode you won't want to miss!

Several weeks ago I interviewed Rose Fan and Molly Dishman of Thoughtworks. Thoughtworks is a global IT consultancy firm, “a community of passionate individuals whose purpose it is to revolutionize software design, creation and delivery, while advocating for positive social change”. In part 2 of this 3 part conversation we discussed Molly's biggest influence, the interview process at Thoughtworks, Lean Enterprises and post-agility, tech's fixation on labels, continuous deployment and a me-too culture, determining how to help the client, journey mapping, Conway's Law, collaboration and breaking down barriers, disruption and the threat of startups, and ways to build inspiration and excitement.

In episode 2 of a 3 part conversation with Chuck Durfee, Agile Coach, Development Manager, Agile Denver Board Member Emeritus, recent MBA graduate, recovering developer, and friend of neon tapirs everywhere we enjoyed a far-ranging conversation. We discussed the following: the spreading of ideas, developmentally driven organizations, people innovation, the agile mindset, Montessori education, language learning, design patterns, Conway's Law, organization designs, the scarcity mindset, the limits of the industrial model, exploratory play, and how structure relates to creativity. And now welcome to the second episode of a 3 part conversation with Chuck Durfee.

James Lewis visits with Agile Amped at the first ever Agile Alliance Technical Conference to discuss microservices and Conway's Law. James is a self-described "coding architect" with Thoughtworks out of London, where he often leads teams and helps them build better software. Conway's Law, according to James, essentially says that how your teams look is how your software will end up looking. Says James, "If you have loosely coupled teams, then you have loosely coupled software. If you have tightly coupled teams, then you'll have tightly coupled software." A modular approach to building software, however would enable you to change software more easily and quickly without having to throw the whole thing out when you need to fix it. Together, these are the topics of James' session at AATC2016: "Microservices and Conway's Law". SolutionsIQ's Neville Poole hosts. About Agile Amped The Agile Amped podcast series engages with industry thought leaders at Agile events across the country to bring valuable content to subscribers anytime, anywhere. To receive real-time updates, subscribe at YouTube, iTunes or SolutionsIQ.com. Subscribe: http://bit.ly/SIQYouTube, http://bit.ly/SIQiTunes, http://www.solutionsiq.com/agile-amped/ Follow: http://bit.ly/SIQTwitter Like: http://bit.ly/SIQFacebook

Devin and Jim talk about the role of leveraging microservices development in middle market companies, mixing classic development with microservices -- with proper shout outs to Martin Fowler, Conway's Law and a small sidebar into Game of Thrones.