cloud2030

We use ChatGPT to live create DevOps, automation, Ansible, TerraForm, Python, and interact with different clouds to get advice on how to set up clouds. This discussion includes a screen share session, so if you're listening to this audio there will be times when we are talking about something you can't see but I do make a point of working to explain what we're doing. There’s also a video of the screen share session if you prefer. Video: https://youtu.be/hU7pUDfliGk Transcript: https://otter.ai/u/MPvT7SP0FCSe02asm8_iSunXz6o?utm_source=copy_url Image: https://www.pexels.com/photo/pink-background-with-speech-bubble-1111369

What does it take to make a good decision? We discuss an interesting take on this as we integrate the topic of how to sell into situations, and selling is the ultimate drive in a decision. Our conversation mixes the challenges of making decisions as a leader with the challenges of selling into organizations where people have to make a decision to choose your product. It also includes tips on how to frame decisions, how to position decisions, and more. If you engage in projects and selling them to your boss, supervisor, company, peers, reports, etc - you need to be able to understand why it is important to move forward and make a decision or change. If you're not able to sell, you’re not well equipped for being a leader. Transcript: https://otter.ai/u/1SRbrNbmISOgTUyV2Xp8AZtmKZU?utm_source=copy_url Image: https://www.pexels.com/photo/man-looking-at-a-vintage-car-3056057/

What can we expect generative AI to generate and is it going to produce good code? Today we talk about Gluecon and generative DevOps and the different concepts and capabilities around it. What impact is it going to have on developers? How do we control that? Today’s discussion was in preparation for our session on June 13, where we're going to group program GPT to see what type of DevOps coding skills we can prompt. We talked about the necessity of prompting in this session and covered some tips to help you think about how to be a better prompt engineer, a skill set that everybody's going to need to have in the next months if not years. Transcript: https://otter.ai/u/lsye_htH0-wksAOrqgbUu5TCtpU?utm_source=copy_url Image: https://www.pexels.com/photo/man-welding-round-window-frame-2965260/

What actually is used to describe the provenance and information that comes with our data? Today we discuss metadata and the governance, security, hint, domains, date that accompany data in ways that in some senses are more important than data. How can we move, change and transform data? We had a really robust conversation about how access to data is so critical in actually understanding how data is used. This is a topic we struggle with: figuring out the naming, how things work, and the context. More than anything else, the context makes things challenging. As you listen to this, think through how challenging it is to define data, data governance, and using data effectively. Transcript: https://otter.ai/u/VE2u_jTwG_h4z9ewfI0bya7kvmg?utm_source=copy_url Image: https://www.pexels.com/photo/cheerful-black-teacher-with-diverse-schoolkids-5905918/

What would our systems look like if we didn't have Kubernetes? We started this discussion with platform engineering and its associated challenges. In talking about platforms, we covered ways in which people can consume infrastructure more effectively. That segwayed directly into ways in which Kubernetes could be changed under the covers, used for virtualization use for non traditional containerized automation. This episode is a pretty thorough review of alternatives to Kubernetes, and the ways in which Kubernetes misses the mark. Transcript: https://otter.ai/u/0qX-qloVOzAQ47LgpS2A9yXsoWs?utm_source=copy_url Image: https://www.pexels.com/photo/wrecked-ship-2336927/

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/