Today we riff on vibe coding, and we talk about the human and economic impacts. Can this agentic coding paradigm the use of AI and how will it impact people just starting their careers or building real applications? What is the trajectory for AI, generated systems and code and what is the risk of AI slop?
DevOps Lunch and Learn focuses on home labbing versus enterprise use cases and why it is so tricky to satisfy the home user with enterprise products. This really is a dilemma because we love to see more crossover and we’re going to talk about why.
In this episode, we dive into all things quantum computing, starting from the idea that Microsoft managed to put a new quantum silicon chip together. We go all over quantum from compute to entanglement and everything in between.
We step back in this episode of our Tech Ops series and talk about cloud self managed infrastructure and how you balance the competing concerns. We started from a report that RackN had commissioned talking about on premises Kubernetes, and mixing that into your IT infrastructure.
Can you have a cloud broker? Can you do multi cloud, some sort of tried and true topics for cloud consideration, but through a new filter and through this repatriation idea of mixing and matching your IT Infrastructure?
Do nuclear power and a potential renaissance in nuclear power, driven by the voracious power demands for data centers, have the potential of becoming accepted, local and an economic boom for communities? If you’re scratching your head thinking, no way, maybe this conversation will change your mind. Enjoy!
This podcast episode explores the challenges of process improvement in IT operations, using examples from data centers, automotive, and cybersecurity.
The discussion covers the slow evolution of secure boot, the difficulties cloud providers face in translating their processes to the broader market, and the emergence of vehicle-to-anything ecosystems. The group delves into the need for standardization and security in vehicle ecosystems, as well as the policy management and automation challenges enterprises face.
The conversation also examines the balance of trust in technology versus human expertise, particularly around the use of AI and the risks of generative AI. The CrowdStrike incident is analyzed, with debate around the responsibility of CrowdStrike, Microsoft, and Delta’s operational controls. The impact on cyber insurance and the need for broader risk management approaches are also discussed, highlighting the interconnectedness of process improvement and risk management, and the call for greater industry collaboration to address these challenges.
This episode explores the intersection of infrastructure automation and security through the lens of the Crowd Strike outage. We’ll discuss the tension between maintaining stable, reliable data center infrastructure and the need to embrace change and innovation.
Recent events like the CrowdStrike outage demonstrate the paradox that infrastructure teams face. We’ll dive into the importance of having multiple control planes and standardized processes that can adapt to rapid industry changes.
We start talking about walled gardens and the momentum and push that causes us to get into vendor active environments in this episode. This is going to be a multi-part discussion where we look at the drivers of AI in the future.
In this case, we used up a lot of time before this recording talking about Kubernetes and what’s next for Kubernetes and containers, as well as how that ecosystem has been shaping up. This conversation is about the wall gardens that could be broken down, and in some cases, have actually been built taller because of containerization and Kubernetes and infrastructure and how infrastructure works.
After that background before going into the discussion, we pick it up on how these ecosystems and walled gardens are self reinforcing as well as chinks in the armor that will allow us to go back to interoperable standards.
Martez Reed and I have an in depth conversation about the challenges of propagating technology inside of enterprises, this core challenge of selling silos and individual technologies. What Martez describes as beneficial tool sprawl versus building up systems and integrating things and end to end technology. This is what I’ve been calling infrastructure pipelining. We break down what’s going on in the street related to Open Source technology, Kubernetes, other aspects of what’s happening and how things fit together in an interesting and dynamic way.
TechOps series episode 3 covers how to automate against API’s. We discuss exactly the ways in which you can use API’s effectively, and ways you can run into trouble. We also discuss how we should be consuming API’s, both as a consumer but also in times when we have produced API’s. Many ideas discussed were pulled from learning how people consume our API’s and what we can do to help make them better and safer.
Enjoy this broader TechOps series where we are diving in deep in tips and techniques that improve your journey as an Automator.