Submitted by Gary Fleming
Our software lives in an entropic state. The world changes around it: new bugs appear, new versions, new operating systems, new hardware. Our systems must change or face eventual demise.
We often adopt approaches to continuously deploy our systems, but what if we had tools that let us continuously upgrade them too; pushing the entropy back a little bit each day.
We'll talk about CI/CD, and some advanced practices we can use to keep our systems continually fresh, continually rejuvenated.
Gary is an agile provocateur, software crafter, and lean mercenary. His main hobby is to try and help companies to build better software in better ways. Sometimes this is by helping them with the messy human communication side of agile, and sometimes it's through teaching better software crafting practices - but it's usually at least some of each. Coaching, mentoring, writing, and showing; whatever helps in the context. You'll find him at various local meetups trying to both share what he knows and learn from his peers.