February 2021 Summaries

GitOps is a paradigm that uses version control systems to manage infrastructure as code, but it can lead to frustration and decreased satisfaction when teams scale up and introduce more YAML files and microservices. This happens because the number of suppliers (individual developers) increases, leading to a higher likelihood of failure, which in turn makes it harder to ensure audit trails. To mitigate this issue, the key is to focus on controlling the input by removing human error and using baseline configurations that can be standardized across teams. By creating immutable records of application configurations at deployment time, teams can maintain control over their YAML files while still giving developers the freedom to configure their applications.

When evaluating documentation for a new tool or project, consider the developer experience, as it can greatly impact the efficiency and effectiveness of the team. A good getting started guide should have a self-serve option available, allowing users to create an account and test themselves without needing to go through a sales process. The time it takes to follow a getting started guide from beginning to satisfactory conclusion is also a key factor. Dependencies and prerequisites should be clearly stated, and the documentation should suggest common pages or paths for further information. Code examples should be complete, well-structured, and accompanied by explanations of expected output. Reference documentation, such as API endpoint and function documentation, can fill in gaps and provide useful information to readers. Finally, good language, consistent voice, and style guides are essential, and a team's attention to detail and care for their users can be seen in the quality of their documentation.

Monitoring deployment frequency is crucial for achieving and surpassing goals in a DevOps strategy, as it measures how often code is deployed to production or an app store. Top-performing companies identify frequent deployment as a measure of success, with elite teams deploying multiple times per day and low performers deploying only once every six months. Measuring deployment frequency offers insights into the efficacy of DevOps practices within a company, helping organizations understand their workflow, identify broader issues, and make data-driven goals to improve upon it. By regularly assessing deployment frequency, companies can differentiate between high and low performing teams, and use this metric as a barometer for success in achieving continuous delivery and shipping code quickly and frequently.