Why do companies want to be SOC 2 compliant? Because it's proof that you care about security. And operational excellence. Customers like that. Turns out, you can get SOC 2 quick wins pretty easily by having developers follow the Git best practices in this guide. If you're a technical leader working with CISO - or acting as one - this is a must read:
Story of how the Tinder team migrated (swiped right?) to Kubernetes. It took them nearly two years, but now infrastructure is no longer a task for Ops. All engineers now share the responsibility and have control over how their applications are built and deployed with everything as code.
Karolina Szczur points out that technical debt is becoming an excuse for missing deadlines, employee dissatisfaction, and user experience compromises, and details what is and isn't technical debt.
These things typically fall under the category of “things I’ve been wanting to play with but haven’t gotten around to it yet”. Zach Schneider does a deep dive on this stack for the rest of us.
Lee Briggs writes about his experience giving AWS Fargate a proper try to see if "serverless computing will really kill the Ops engineer", and compares it to Kubernetes.
Teri Radichel writes about the increasing popularity of the term guardrails in the cloud security space, and explains how Datree is one such tool for setting guardrails on GitHub 💂
Join 5,000+ subscribers of hand-curated
Git and DevOps articles