SIGN UP: https://skillsmatter.com/meetups/7807-domain-architecture-isomorphism-i-fought-conway-s-law-and-the-law-won
Dylan Beattie : "Domain Architecture Isomorphism: I Fought Conway's Law (And the Law Won)"
Most developers have encountered Conway's Law (https://en.wikipedia.org/wiki/Conway%27s_law) at some point in their career - the observation that "organisations that design systems are constrained to produce designs which are copies of the communication structures of those organisations". In twenty years of professional software development, Dylan has seen this pattern first-hand time and time again. He's seen it on small projects, on large projects, on colocated and distributed teams, and he's now thinking that if Conway is right - and the evidence rather suggests he is - then it's very likely that the rest of us are Doing It Wrong.
Once you accept the the tendency for systems to end up reflecting the structure of the teams that build them, it suddenly becomes very clear why a lot of software projects don't go according to plan. Your architect says you're going to use an API instead of direct database access - but then you sit your back-end developers right next to your DBA and give them a deadline to hit. What do you think's going to happen to your abstraction layer? Or you decide you're going to have an API team in London working with an app developer in Belarus and a web team in Ukraine, and then you wonder why your system's communication layers are causing performance problems?
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.
Dylan Beattie is a systems architect and software developer. He's been building interactive web applications on the Microsoft stack since the days of Windows NT 4. Today his main interests are HTTP APIs, user experience design, and distributed systems. Dylan lives and works in London, and he's on Twitter @dylanbeattie (https://twitter.com/dylanbeattie)
Oded Coster: "How to ask good questions on Stack Overflow"
StackOverflow and the rest of the StackExchange network are invaluable resources for professional developer - but to get the most out of them, you need to know how to ask the right questions. In this talk, Oded Coster will discuss the valuable and often-overlooked skill of how to ask good technical questions - "it turns out this isn't as common sense as one would expect", says Oded. He'll offer general guidance on asking questions, and a specific focus on using the StackOverflow platform to ask technical questions - and hopefully get some answers.
Oded (http://stackoverflow.com/users/1583/oded)is a developer at StackOverflow, where he works on the StackOverflow codebase - and with over 315,000 reputation points, he clearly knows a thing or two about asking and answering questions. He's on Twitter as @OdedCoster (https://twitter.com/odedcoster)