Have you ever run into an issue that you just know someone has solved before? A situation where you stop yourself mid-function-declaration and say “What am I doing? Why reinvent the wheel here?” and then find that a Stack Overflow search quickly serves up the copy-pasta you ordered? In the world of software architecture, we call that copy-pasta a “design pattern”. Design patterns are architectural solutions to common problems. In this talk, I’ll make the case for software design patterns and explain how to get them adopted by your teams. This talk is based on my popular article “The Importance Of Design Patterns When Leading Large Teams". ## In this session, we’ll discuss: 1. What design patterns are and why they exist. 2. Their effect on projects of various sizes. 3. An application I built with a team, the decisions we made along the way, and what patterns we considered for different scenarios vs what we ultimately went with. 4.How you can take things too far with patterns through an example of a time when I did just that. 5. How to maintain these patterns through facilitated recurring conversations. 6. Selling the idea of software design patterns to your boss as well as your team. ## This session is for you if: You’re a junior developer just getting interested in the concept of how software is put together from a high-level view. You’re an individual contributor on a team and want to be more informed when talking about software design patterns among your peers. You’re an individual contributor and want to know how to affect change from a non-leadership perspective on your team. You’re a technical leader and want to hear a more broad perspective of when to consider using software design patterns.