In this talk, Dylan will explore the idea that we should be designing our systems first, and then restructuring our teams to reflect the system design. We'll look at some common communication structures - including some things you probably do already that you never realised were communication structures - and how those structures affected the outcome of the systems they helped build. We'll discuss how you can apply common patterns to your teams as well as your code, and we'll talk about how to sell the idea to your boss before you start moving desks around.
YOU MAY ALSO LIKE:
- Have I Got .NET For You?! (SkillsCast recorded in September 2019)
- Functional Concurrency in .NET with C# and F# with Riccardo Terrell (Online Course on 1st - 4th December 2020)
- Build High Performance Stream Processing and Workflows with TPL Dataflow (SkillsCast recorded in October 2020)
- What’s New in .NET Core 3.0 and .NET 5.0 for Performance and Memory-Aware Folks? (SkillsCast recorded in October 2019)
Domain Architecture Isomorphism: I Fought Conway's Law (And the Law Won)
Dylan Beattie is a systems architect, developer, and Microsoft MVP, who has built everything from tiny standalone websites to large-scale distributed systems. He created his first web page in 1992, and he's been building data-driven interactive web applications since the days of Windows NT 4. He's currently the CTO at Skills Matter in London, where he juggles his time between working on their software platform and supporting their conference and community teams. From 2003 to 2018, Dylan worked as webmaster, then IT Manager, and then systems architect at Spotlight (www.spotlight.com), where his first-hand experience of watching an organisation and its codebase evolve over more than a decade provided him with a unique insight into how everything from web standards and API design to Conway's Law and recruitment ends up influencing a company’s code and culture.