#121: Hooray! You’ve finally gotten around to implementing your infrastructure as code. But tomorrow is a new day with new problems that you didn’t plan for in Day 1. Now what do you have to do in order to continue moving forward? Today, we speak with Tim Davis about day two and many other topics around infrastructure as code.
Order your copy of Essential Infrastructure as Code at:
and be sure to use the code “podparadox20” to save 40% off of Essential Infrastructure as Code and any other purchases at Manning Publications.
If you like our podcast, please consider rating and reviewing our show! Click here, scroll to the bottom, tap to rate with five stars, and select “Write a Review.” Then be sure to let us know what you liked most about the episode!
Also, if you haven’t done so already, subscribe to the podcast. We're adding a bunch of bonus episodes to the feed and, if you’re not subscribed, there’s a good chance you’ll miss out. Subscribe now!
Tim Davis is the DevOps Advocate for env0. Prior to env0, Tim helped build the Cloud and Developer Advocacy team at VMware. His background is in Infrastructure Operations / Architecture, while always focusing on the business critical applications that run the business. While at VMware, his focus area was on DevOps Process / Procedure, and CI/CD Process / Tooling.
Viktor Farcic is a member of the Google Developer Experts and Docker Captains groups, and published author.
His big passions are DevOps, Containers, Kubernetes, Microservices, Continuous Integration, Delivery and Deployment (CI/CD) and Test-Driven Development (TDD).
He often speaks at community gatherings and conferences (latest can be found here).
His random thoughts and tutorials can be found in his blog TechnologyConversations.com.