Operations | Monitoring | ITSM | DevOps | Cloud

The Confident Commit | Episode 6: Architecture meets delivery with Chris Richardson

Rob interviews Chris Richardson on how engineering metrics can help teams evaluate the effectiveness of their architecture. The two discuss how a team's architecture can enable or inhibit their ability to make changes quickly and confidently. How do you balance rapid delivery and finding product-market fit with getting to a stable, workable system over time? Tune in today!

Securing pipelines through secret management

Secrets management plays a critical role in keeping your pipelines and applications secure. While secrets management tools help, you need to implement best practices and processes to successfully manage secrets in a DevOps environment. Standardizing, automating and integrating these processes also helps secure secrets by reducing the chance of human error.

Reducing microservice overhead with shared libraries

It’s a common story: the product team gets early success and grows into a large monolithic code base. While everything is in a single code base, features can be added quickly. This is partly due to the ability to leverage shared code across each feature in the codebase. When your team is adding a new feature, a developer can leverage the existing codebase for needs such as logging or special error handling.

Featured Post

3 ways to motivate your developer team with metrics

Metrics are essential to assess how developer teams and organisations can work smarter and improve software delivery as a whole. Execution metrics, including the likes of throughput, delivery and number of deploys, are mostly looked at to determine how a team performs, and if overall, they are efficient. But, while useful, these metrics alone can sometimes be a distraction. For individuals, they may not be inspiring to achieve, and for businesses, they may not provide a complete picture of results - at least not without connecting them to a bigger goal or vision.