Tech debt affects just about every software organization. For better or worse, speed is one of the core tenets of the software development industry – the rush to build more, add new features, and find solutions fast can drive short-term growth for small organizations and add value for large companies. But haste, as it usually does, makes waste: The mass of suboptimal code, redundant services, and bottlenecked processes that we call tech debt.

Following good practices in the Day 0, Day 1, and Day 2 software development lifecycle can help you create a consistent environment that is easier to maintain. In this blog, we will deepen your understanding of how to make Day 2 operations succeed, and how high performing teams put Puppet to work on Day 2 to make a stronger, less manual, software development lifecycle.

In early 2023 Betadots together with Vox Pupuli adopted the Puppet containers and so this article has been updated to contain the new locations. Details of their adoption can be found here. If you’ve ever wanted to get started with Puppet or Docker — or both — you’ve probably faced a bit of a conundrum. Should I use Puppet to deploy Docker on my nodes, and then use Puppet to define container images?

Threat vulnerability management, and managing your attack surface, are critical in the battle against cyberattacks. At some point before an successful attack, the internal process to manage threats and prevent access to sensitive data failed. How could they have done things differently? Were they just managing too much, too often, without the resources they needed?

The definition of a platform engineer can be slippery. Ask several IT professionals “What does a platform engineer do?” and you might get several different answers. One platform engineer might be at the intersection of DevOps, AppSec, architecture, and SRE, while another might broadly support infrastructure for all developers in their organization. (Sometimes, in less successful teams, they’re essentially a DevOps engineer with a fancy title.)