We’ve all heard of the idea of ‘software architecture’. We’ve read books about domain-driven design and event sourcing, we’ve been to conferences and learned about micro services and REST APIs. Some of us remember working with n-tiers and stored procedures... some of us are still using them. But the role of a systems architect is still one of the most misunderstood things about the software development process. What does the architect actually do? If you’re working with a systems architect, what can you expect from them? And if you are a systems architect, what are your team expecting from you? In this talk, Dylan will share his own insights into the idea of architecture as part of a software development process. We’ll explore some popular architectural patterns and processes — and a couple of obscure ones as well — and look at how, and when, you can incorporate those patterns into your own projects. We’ll talk about how the idea of software architecture has changed over time, and share some tips and advice for developers who find themselves working with architecture as part of their role.
Dylan wrote his first web page in 1992 and never looked back. He’s been building data-driven web applications since the late 1990s, and has worked on everything from tiny standalone websites to complex distributed systems. He’s the CTO at Skills Matter in London, he’s a Microsoft MVP, and he’s a regular speaker at conferences and user groups, where he’s spoken about topics from continuous delivery and Conway’s Law to the history of the web, federated authentication and hypermedia APIs. When he’s not wrangling code, Dylan plays guitar and writes songs about code. He’s online at dylanbeattie.net and on Twitter as @dylanbeattie.
#codefest #codefest2019 #CodeFestX