Have you ever found yourself copy-pasting the same Terraform or Bicep code across different repositories just to change a few variables? It feels efficient at first, but it quickly becomes a maintenance nightmare when you need to push an update to everyone. How can we build a setup where we write code once and reuse it across the entire company? I want to share a practical strategy for organizing your repositories that separates the "how" from the "what." We will walk through how to structure your code and configuration in a way that provides flexibility for teams while keeping the product/platform team in the driver's seat. Join me and learn how to set up a scalable git strategy that works for both platform teams and product companies.
Patrick is a passionate consultant with broad knowledge of infrastructure and security aspects of IT. As a Cloud Architect and Specialist, he helps customers by designing, implementing, and assessing cloud architectures and solutions in alignment with his customers’ business and IT objectives. Throughout the past 16 years, Patrick has accumulated a broad experience in Infrastructure, Security, and Consulting, mainly at companies that relied heavily on Microsoft technology. He applies state-of-the-art technologies and concepts, including the cloud and DevOps, to help his customers create business value. His approach is one of honesty and building relationships, which always makes him a trusted advisor for his stakeholders. Patrick has a clear and analytical mindset and is a consultant with excellent communication and presentation skills.