If you read DevOps’ish, you already know I spoke at ChefConf 2018. I was able to meet 1,400 new friends while I was in Chicago (not really but kinda). I presented my talk, DevOps is Not War to a standing room only audience. From a speaker’s perspective, I have never felt more prepared for a talk. There were speaker office hours every week for 10 weeks before the event to address any questions we may have had....
I recently spoke at AWS Michigan about cloud migrations. The talk wasn’t AWS specific but we sure did talk about it a ton. From defining cloud to addressing priorities to preventing cost overruns we covered a lot during the meetup. I was peppered with questions by a lively audience. After speaking on stage at DevOpsDays Atlanta 2018, there was this awkward moment for me when the first question was asked. I wasn’t mentally prepared for questions during the talk but, adjusted quickly....
Abstract “Migrating to the cloud saves money!” “Not running your own infrastructure reduces your bottom line!” “Lift and shift is a legitimate first step towards moving to the cloud!” These are all potential pitfalls if you’re not careful. Proper planning prevents piss poor performance. Using a real chaotic cloud migration as a guide, we’ll walk through the pitfalls of cloud migrations and how to avoid them and the terrifying vendor lock-in (when it makes sense)....
A co-worker and I needed to remove all instances of a binary blob from one of our git repos a while back. This was a lot harder than I thought it should have been, in my opinion. However, distributed version control is not really designed to easily allow folks to delete every instance of a file. But, if you ever run into a case where you do need to expunge a file in git here is how we did it....