Be the first to like this
We accept that automating configuration requires a higher initial investment, but saves time and improves reliability from then on. But when it comes to our own work, we often get tangled up in opening tickets, linking them, peer review, running tests, announcing changes… so many tedious tasks that reduce our agility and distract us from the task at hand at exactly the wrong moment. So why not automate them too?
Process contributes to quality, and that’s unavoidable, so we usually accept the tradeoff. I’ve taken automation one step further and automated *everything* I had to do manually so I can focus on the content of my commits. I’ll share the ideas and tools I use when working on Rudder (but the concepts really apply to any development workflow, including infrastructure as code).