The article delves into managing and organizing GitOps environments using Argo CD, emphasizing the separation of Kubernetes manifests and Argo CD application manifests to prevent complications and maintain clarity. It outlines best practices for structuring Git repositories, advocating for a three-level approach that includes Kubernetes manifests, Application Sets, and optionally, an App-of-App for bootstrapping clusters. The discussion highlights the pitfalls of mixing manifest types, using templating at multiple levels, and working at incorrect abstraction levels, advising against these common anti-patterns. It recommends using multiple Git repositories, ideally one per team, to enhance performance and usability, and stresses the importance of keeping infrastructure applications separate from developer applications. The article underscores the utility of Application Sets for efficiently managing multiple applications across various environments, facilitating a more streamlined and scalable approach to deploying applications with Argo CD.