The Right Tool for the Right Job
Not every infrastructure problem deserves the same solution. Puppet for configuration management and compliance — because state enforcement and auditability matter when you’re managing a fleet. Ansible for automation and one-off tasks — because not everything needs a persistent agent. Containers for ephemeral, process-heavy workloads — because some applications are built to be disposable.
Every problem deserves its own solution, neatly applied.
What this looks like in practice:
- Puppet module development, deployment, and fleet management
- Ansible playbook design for automation and orchestration
- Container strategy (Docker, Podman) for application workloads
- Bare-metal provisioning and lifecycle management
- Infrastructure testing and compliance validation (InSpec)
- Fixing what’s already there — a bad implementation doesn’t always need a migration, sometimes it just needs doing right
- Hardware revival — extending the life of existing servers well beyond their accounting write-off. In a market where big tech is buying up all the RAM and GPUs, keeping solid hardware running longer isn’t nostalgia — it’s economics
Who this is for: Operations teams and infrastructure engineers who need reproducible, auditable, and well-governed infrastructure. Also: anyone whose current setup was built with good intentions but needs someone to untangle the results.
This is a dedicated page for my infrastructure as code work. I’m expanding it with case studies and detailed service descriptions. In the meantime, everything above is accurate and current.