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.