What’s After Twitter?

We dig into the news of the day instead of a scheduled topic on today’s podcast. This news was about Twitter, and what is going on in the social media landscape.

We have a fantastic 2030 style conversation, not specifically about Twitter, or even its new owner, but social media and its needs, how people think about social media, what societal purpose it serves, and how we construct the back ends to support those systems.

We talked about alternative platforms and historical platforms, as well as objectives and benefits of a social media platform including content moderation and who pays for it.

A fascinating conversation for everybody who’s consuming social media.

Transcript: otter.ai/u/yLpHcxsbpGojZgBuckid_TLT7JI
Image: www.pexels.com/photo/green-grass…in-nature-7987527

Rob’s Hot Take:

In the November 3rd Cloud 2030 Podcast episode, Rob Hirschfeld reflects on the change of ownership on Twitter, emphasizing the critical role of content moderation in the success of a social network. The discussion underscores the importance of determining who bears the responsibility and cost of social content moderation, whether it’s advertisers with specific expectations or independent server owners investing time and resources. The evolving landscape of social media prompts a consideration of governance, responsibility, and enforcement of rules in ensuring a safe and effective virtual community. The full podcast, available at the2030.cloud, delves into these insights, inviting listeners to engage in the ongoing conversations.

Kubecon Retrospective

Klaus and I go through what happened at the Kubecon North America event in Detroit. Specifically, lessons learned in watching how the community reacts to new technologies like CRDs, declarative programming, and cluster APIs.

We also discuss the health of the community and the operators and vendors who were involved.

We give our impressions and insight – this conversation deep dives into practical use and futures in Kubernetes.

Transcript: otter.ai/u/8sNj_ZMTbKuJxAhOZhlvLAckWhc
Image: www.pexels.com/photo/elderly-man…e-window-7551662/

Rob’s Hot Take:


In the November 1st DevOps Lunch and Learn, Rob Hirschfeld reflects on the Kubernetes KubeCon retrospective, highlighting the profound impact beyond a platform. The adoption of Custom Resource Definitions (CRD), operators, declarative programming, and GitOps represents a fundamental architectural shift, transforming how applications are built and architected. This shift, witnessed in cloud-native Federation and architectures, marks a significant departure in thinking and process, redefining how systems are addressed and services are communicated. The podcast encourages a broader understanding of the trend, inviting listeners to explore these transformative concepts and join the ongoing discussions at the2030.cloud.

Deep Dive into Distributed ID

Distributed ID is a web three concept of being able to use zero trust and identify users without having a central authority.

In this conversation, we talk about critical concepts like Open ID trust government actions, and how this could be influential and important in a web three and IoT context.

We really drill into how the system works, and I know you will enjoy the conversation

Transcript: otter.ai/u/X_5lffVEG0LUTgsyoDOx5sJDwYM
Images: www.pexels.com/photo/person-putt…rt-on-bag-842961/

Cloud2030IdentityDistributed IDWeb3

Cloud Service Providers vs “The Supercloud”

How does the moniker Supercloud apply to how cloud providers are changing over time? Specifically when facing market pressures, trying to lock in, get bigger and become essential. Today we discuss the changing nature of service providers, specifically cloud providers.

This topic has been coming up on Twitter, and I know you will find this conversation fascinating. It talks both about the hypothetical and very practical drivers behind concepts like supercloud.

Transcript: otter.ai/u/MjuLlkt2JO095bMgPHi-rqeaqi8
Image: www.pexels.com/photo/flying-airp…the-sky-12846027/

What We’re Watching At Kubecon

How do Helm charts and operators interact with Kubernetes? Today we have a fascinating discussion about the interesting components of Kubernetes including Helm charts, admission controllers and things that are changing and being revised and updated.

We discuss potential topics in anticipation for Kubecon, and if you’re at all interested in Kubernetes, whether you’re attending the conference or not, you will find this to be a must follow list of topics related to Kubernetes.

Transcript: otter.ai/u/I9Fyk_wiGxwvtha_tESikR2Bj3U
Image: www.pexels.com/photo/man-in-blac…building-5615440/

Project Mgmt Vs Development Process

Our discussion about development methodologies quickly turns into one about product management methodology.

Those things are interlinked, and we spend a lot of time talking about how product management and the influence on user and operational experience has been transformed by the forces of the market. We also discuss how difficult it is to then organize team development processes to fit these quickly evolving, targeted product delivery challenges.

It’s a fascinating conversation about just how interlinked our development process is to the way we consume products in general.

Transcript: otter.ai/u/_Kljix8Hom5nhuhMbkDISjOL6fM
Image:www.pexels.com/photo/newlywed-co…-tongue-12194401/

Rob’s Hot Take:

In the September 29th Cloud 2030 Podcast, Rob Hirschfeld delves into the challenges of product management and its intricate connection with the development process. Emphasizing the difficulty of product management, he notes the impact of compartmentalization and siloed activities on collaboration and integration across teams. The conversation explores the critical need for cross-team discipline and collaboration, highlighting its absence in current practices and its impact on what is built and how it is built. Hirschfeld invites listeners to engage in the ongoing discussions at the2030.cloud and share their perspectives on these challenges in product design and development processes.

Reading The Analyst Tea Leaves

We talk about understanding analyst reports and engaging with analysts. How do analysts shape the industry and the industry shapes the analysts?

Today we discuss how every part of this ecosystem has to work together in order for us to build serviceable technology, because fundamentally, we count on the analysts to help understand what’s ready, what the problems are, and what’s working or not working in the enterprise.

It’s easy to pitch stuff, it’s much harder to use stuff and sell tech, and the analysts are a reasonable filter for that, and we break down how and why.

Transcript: otter.ai/u/A3BlbqbPObA1_2erEfKZsFPqURs
Image: www.pexels.com/photo/a-person-ho…-a-spoon-3889850/

Rob’s Hot Take:


In the September 27th Cloud 2030 Podcast, Rob Hirschfeld provides insights into the dynamics of reading analyst reports. The discussion highlights the bi-directional nature of communication between analysts and enterprise customers, emphasizing a feedback loop where analysts absorb insights from the market while customers are influenced by market buzz and marketing efforts. Hirschfeld encourages participation in these conversations at the2030.cloud, urging listeners to join roundtable discussions and make their voices heard in this collaborative space.

Learning about eBPF Applications

Special guest Bill Mulligan (twitter.com/breakawaybilly/) talks to us about the use cases for BPF and how it works.

We discuss eBPF, the kernel extensions that allow you to write small programs that work inside of kernel space in a safe sandbox way. These have a lot of applications, and they’ve been creating a lot of hype inside of the Kubernetes community as a way to address networking shortfalls.

Our conversation starts broad, but eventually zeros in on eBPF. I know that you will learn a lot about how eBPF can enhance and improve your infrastructure operations environment.

Transcript: otter.ai/u/VhW6tKfPHD0yky63eDneQ3dIScQ
Image: www.pexels.com/photo/cobblestone…-sandpit-8180645/

Getting the Right Talent And Staffing

How do you build, manage and fund your systems? Today’s episode is about talent, staffing and hiring the right people to do the job for you.

How you make hiring decisions is inexorably linked to how you think about solving, funding, and structuring solutions around those problems. You cannot hire people without also having straightforward answers for those questions.

We have a fantastic conversation about staffing, that we find to actually be about building the foundations for your hiring.

Transcript: otter.ai/u/DPCdAh4CiJPXOQss2WpX2INysfA
Image: www.pexels.com/photo/cute-girls-…rn-house-5859723/

Mentoring Jr DevOps

How do we help junior people build the right skills to do advanced automation system administration, and actually build systems that are resilient and robust? Then, after understanding that that is a learned skill that’s predominantly learned by doing the work, troubleshooting.

We started the conversation talking through how to teach troubleshooting and find opportunities for that. But we transformed the discussion into the challenge of teaching people skills that they then walk away with, that, as you’re mentoring people, you’re increasing their value, and potentially giving them the keys to leave and find a better job.

We talked about this as an industry trend, and some expectations on what you can do about it, and how you can approach that situation. Overall a very robust conversation about building great teams, through junior engineers, and what it takes to be thorough and complete in a process like that. Both from what you can do, and what you have to watch out for.

Transcript: otter.ai/u/cOP6v9HEYv6_YVrrRwA_sxjvNaQ
Image:www.pexels.com/photo/a-girl-usin…noculars-9290029/

Rob’s Hot Take:

In the September 13th Cloud2030 Podcast, Rob Hirschfeld shares insights on mentoring junior DevOps engineers, emphasizing the importance of troubleshooting for their learning process. He highlights the hands-on nature of operations and admin work, where individuals encounter challenging problems, learn on the job, and understand solutions by fixing issues. Hirschfeld stresses the need for a supportive environment that allows junior team members to learn without time pressure, fostering a culture that encourages experimentation and learning through doing.