This week’s episode of Day Two Cloud is an open discussion between me, Drew Conry-Murray, and Ethan Banks regarding the successor to Andy Jassy as AWS CEO. Drew had made an off-hand comment suggesting that Amazon could put a ham sandwich in charge of AWS and it would still perform just as well. I challenged Drew to argue his point, and Ethan took up the counterpoint. It’s a lively discussion and I highly recommend giving it a listen.
This week’s Day Two Cloud episode features Calvin Hendryx-Parker talking to me and Ethan about moving to an Infrastructure as Code approach and hosting that approach in the cloud. We really hit the ground running, and soon we were digging into the details of how to separate application and infra code, being kind to your future self, and taking advantage of cloud native services like Lambda.
Consulting is the type of job that can really push your abilities to the limit, and independent consulting does that while also making you an accountant, marketer, and HR. In episode 84 of Day Two Cloud, Ethan and I talk with Anthony Nocentino and Michael Jenkins about their experience working as consultants. We all share how working for yourself as an independent consultant can be incredibly rewarding and also soul destroying.
Well? Should it? This was a tremendous episode with Dwayne Monroe where we discussed the concept of a public cloud available as a utility or at least a public offering for educational institutions and lower income folks. We had a good debate, especially over whether the government is capable of successfully executing and managing such a project given all the bureaucracy that tends to cruft over most well-intentioned government programs.
This week’s Day Two Cloud episode features Matt Klein, Lyft plumber and writer of Envoy. We discuss not only the need for service meshes, but more broadly the need for any new technology within your organization. Based on previous panels I have seen Matt participate on, I knew this was going to be an interesting episode. But I had no idea how just how excellent it would be! Seriously, give it a listen.
During the episode, Matt made the argument that companies should not adopt new technology for its own sake, rather they should be laser focused on what the business needs are and ensure that current technology is meeting those needs. Assuming it is, then they should not try and introduce new technology, as that will introduce new bugs and potential instability. On the surface, I broadly agree with what Matt said, but I tried to articulate a counterpoint. I did so badly in the moment, so I thought maybe I could try and flesh out my thoughts here instead.