"I've generally found that there's really two groups of people. There's the people that have gone through the process of deploying a whole bunch of infrastructure, suffered the pain, and spent those six to 24 months and understand it, and then there's the people who haven't, who are newbies." -- Yevgeniy Brikman An effective way to get good at something is to capture the lessons learned from those ahead in their journey. Drawing from our lessons learned working with Git, then taking a step back and applying a beginner's mindset, we wrote this fun list of 10 Git commands that don't actually exist:
In this video from his QCon presentation, Yevgeniy Brikman talks about lessons learned from deploying infrastructure code library to production for hundreds of companies. Transcript included.
Anyone who built software for a while knows that estimating time to completion is hard. Erik Bernhardsson believes this is really just a statistical artifact and sets out to prove it.
A Git tutorial on how to back up or sync your custom configurations across your systems by sharing dotfiles on GitLab or GitHub.
Kaimar Karu shares his framework for deciding when to invest in trying out a new approach, technology, or tool and shares a few pointers.
Speaking of new approach, the chaos engineering community recently had their Chaos Community Day, where Nora Jones presented common traps to avoid when starting out.
Sebastian Gauder described how they migrated a monolith at a large German retail company into 270 microservices, while taking the number of teams from two up to almost 50 (!).