How do you deal with the weakest link in security? Today we talk through how we can secure systems, all the way from what technical processes put in place to the people involved to legal enforcement, and who pays the price when data is compromised? There's a lot to digest here that comes back to thoughtful ways in which we can deal with the weakest link in the systems. How do we create robust security models? Transcript: https://otter.ai/u/mkup2hKSzyP0PkpxkkoPbnQrNgw?utm_source=copy_url Image: https://www.pexels.com/photo/brown-thread-2072872/

The book Data Cartels by Sarah Lambda serves as a starting point for our discussion today. https://www.amazon.com/Data-Cartels-Companies-Monopolize-Information/dp/1503633713 A dense and thoughtful book, it is straight up the alley of the type of conversations of the2030.cloud has. Our analysis of the book and the challenges it provides - the data compliance governance, the legality, the threat, and broader implications of what Dr. Lambda lays out - are all really important. Today’s podcast is understandable and interesting without having had to go through and read the book, but I still recommend that you do. Transcript: https://otter.ai/u/T5CJzO8pMrpGnLVGo48fOcHcuj4?utm_source=copy_url Image: https://www.pexels.com/photo/lady-justice-and-a-gavel-6077123/

How can you execute on a zero trust strategy and what do you need to keep in mind while building it? Today covers the 101 and 201 levels on zero trust. We had a really good conversation about how it works, what doesn't work, what you need to be prepared for. Even if you think you understand zero trust, you will get something out of this conversation. And if it's a new topic for you, you can also benefit from this pragmatic discussion of zero trust, security and application architects. Transcript: https://otter.ai/u/Z1SO1WuJYT3JmEctZe1-SzlQ_Nw?utm_source=copy_url Image: https://www.pexels.com/photo/wooden-chair-on-a-white-wall-studio-963486/

Software bills of materials are one of the most critical, modern software development practices that people should be doing but don't. They have significant impacts in improving security, provenance, reproducibility, and license compliance. The benefits of having a good software bill of materials in our technology industry are incredibly high, both as a producer and a consumer. And yet, this is one of those places where I feel like we have really fallen behind. Transcript: https://otter.ai/u/J3VtBLiQMAuZgfMCOz9K62uKjYg?utm_source=copy_url Image: https://www.pexels.com/photo/photo-of-monumental-sculpture-3810915/

We dig into a topic written about by Eric Norlin or SK ventures about technical debt and AI. In this episode, we discuss the consequences of generative AI could be radically transforming the way in which we generate code and deal with code that has been generated in technical debt. We explore some fascinating concepts about how fast we can iterate, how we change the dynamics of building software, building automation, and the expertise required to architect systems. This leads pretty far down in the path towards disruptive thinking, and how this could reshape the entire industry. Source: https://skventures.substack.com/p/societys-technical-debt-and-softwares Transcript: https://otter.ai/u/MEtVkoNnZeCu0JHa30-jPOcRrj4?utm_source=copy_url Image: https://www.pexels.com/photo/piggy-bank-beside-a-flower-4886900/

We continue our discussion of what would the environment look like without Kubernetes? We started with the idea of what if Kubernetes went away, what if there was a copyright or a trademark or an API issue that made us have to abandon Kubernetes altogether? In this episode we played what if scenarios, exploring what made Kubernetes unique, and if parts of Kubernetes or parts of the architectural model could exist outside of Kubernetes? What would be necessary? We identified enough parts of Kubernetes individually where we saw how it itself is an interesting convergence of some core technologies. Nothing new except in the combination of those architectural paradigms, designs and open source models. Through this, we dig into why Kubernetes is so powerful in the market. Transcript: https://otter.ai/u/L7GZRD8-wEnzLIJL5_nLCPfbogY?utm_source=copy_url Image: https://www.pexels.com/photo/wreck-of-sunken-ship-in-middle-of-bay-12102304/

NOTE: This is Rob's Gluecon topic on 5/24. Save $300 if you register with speaker300 at https://www.gluecon.com We dive into the question of whether or not generative AI can be used to productively change DevOps automation and the control of infrastructure. We've discussed the closed loop side of using AI to manage infrastructure in the past, but this episode we really dive into the idea of creating automation and using generative AI. Transcript: https://otter.ai/u/VtnznHgydT3_6QSJpkSb3uU2btY?utm_source=copy_url Image: https://www.pexels.com/photo/tossing-fried-rice-in-a-frying-pan-6937457/

We talk about improving the time it takes to make decisions - called time to decision, a topic that we like to address quite a bit. We started with the news of the day around AI, ml Chaffee GP, and learning models. We asked ourselves if AI/ML and generative AI could change the way expertise is used to make decisions and improve the time to the decision for experts. What type of implications would that have in the market? If you've been tracking this subject, I know you will find this exciting and interesting. Transcript: https://otter.ai/u/L3Kb_I4fe0ggAr9nDEhyECSkt5A?utm_source=copy_url Image: https://www.pexels.com/photo/person-touching-black-two-bell-alarm-clock-1198264/

Today we look at what it takes to have much more collaborative building of automation, templates and shared components that are necessary to really drive platform engineering, and not just between teams at the same company. We make components for infrastructure automation that bridges the industry because they can be shared much more broadly, similar to the way we share modules in coding languages. We dug into what it takes to make that type of environment work in automation, and what are the prerequisites of the environment? How do we structure automation? Transcript: https://otter.ai/u/IPyFDG19OCH-UekM7Pbfbg1XJx4?utm_source=copy_url Image: https://www.pexels.com/photo/doctor-operating-a-patient-4421494/

How do we sustain open source? Today we discussed how the commercial models and sustaining models around open source are changing and evolving. We also included some conversations about whether or not generative AI might actually change the economics around that part of open source. We hit on top projects, open source hardware, open source, operating systems platforms, a whole gambit, and how it fits together into a sustainable model for the users, companies, enterprises, and really everybody. We all use open source to one extent or another. We have our book club coming up on data cartels, we're going to be discussing it on May 4th and I hope you take the time to read and come join us. Transcript: https://otter.ai/u/MugVjZkIebPMCepjlVb69YQoX9k?utm_source=copy_url Image: https://www.pexels.com/photo/wood-road-landscape-mountain-16179008/