How do supply chain, ecologic, capital, and political issues limit our ability to continue to build big data centers? Today we expand on this continued conversation.
We’re already seeing this in the news, and we need to rethink how we are building a lot of the core infrastructure we depend on. That includes power, data centers, networking and connectivity. Potentially even human logic, which we get into.
The purpose of this conversation was to look at the bigger picture, and then pull it back into how we build IT systems.
How do we build advanced innovative products and companies? We discuss the Chips act and global supply chain of silicon and manufacturing in today’s episode.
We took that apart into its component parts: supply chains, raw materials, power, whether talent, real estate, and put it back together in ways that look forward towards how we think these forces and global politics are going to shape manufacturing for the next decade.
Absolutely fascinating and critical discussion that will impact every single person’s health, their careers, and frankly, what they can buy on the store shelves.
When working with orchestration in automated systems, how do you find the right balance between things that are event driven and things that are workflow driven, or more linear?
We go through some of the history of where we went from linear orchestration (Ansible) to timed orchestration (Chef or Puppet). We also discussed SaltStack, which had an event driven system into it, but didn’t gain the traction that we might have expected as we look at the amount of orchestration systems that are now coming to light.
In this conversation, we address the balance between when you orchestrate and when you want to do workflow and linear transactions, and how to find that sweet spot.
One of the things that we’ve determined is, there aren’t a lot of tools that hit that sweet spot. And I think if you listen carefully, you’ll see why.
How can we structure incentives to build strong, resilient infrastructure? Today we talk about power infrastructure.
There are a lot of commercial incentives for internet providers and for consumers to have good internet, but there aren’t the same incentives for consumers to have reliable power systems. We’re seeing a rash of failures and faults in the grid.
In this conversation, we talk about storage systems and resilience of the grid, not by putting more wires in the ground but by actually creating incentives for people to have independent supplies, and independent sources of generation that can support them.
We continue our hiring advice series in this episode. It’s a really powerful thing to have people who have established careers, think about what would have made a difference, think about what is important when we work with and mentor inexperienced and junior people who are building a career.
This episode is full of thoughtful advice on how to build subject matter expertise, and the ephemeral qualities that make somebody a good leader or a good worker, or what we were calling an executive function.
If you are building your career, or helping mentor people who are building a career, you will get a lot out of this.
What are the challenges of interconnectedness and transparency, specifically concerning Kubernetes and cloud native applications?
We have a fascinating discussion sparked by the question of how exposed we are. What happens when something we don’t know is connected is open and exposed as hackable? What happens when it closes, and we didn’t know?
We talked about how this is inherent in the architecture of cloud native applications and what you can do about it.
This discussion should get you thinking about how to architect not just your applications, but the platforms that you need to connect together to make them work.
How do you build GitOps, infrastructure and systems relying on events and monitoring, when you need to revert to a polling loop, or augment a polling loop with an event system?
Today, we drill into concrete technical details about events and monitoring. We also suggest practical functional advice on how Git Ops works, how systems work, and how you can build a resilient system.
Stick around for a bonus at the end of the discussion, where we talk a little bit about complexity!
How do we handle distributing identity? DID stands for distributed identifiers, and today we talk about Web3 as well as distributing identity.
Distributing identity is not just about people and personal identity, but also about things and how we identify and track different things in a distributed way without a centralized infrastructure. That’s fundamental to what Web3 is talking about.
How do we break down the centralization that we have been building over the last 15 years of what Web3 people call Web2, and look at ways to do it in a decentralized way where the trust is between the parties involved? Where it’s set up in a way that you don’t have to have a centralized trust authority.
We spend a lot of time talking about this, what the spec is, what it means, and looking at it in a broader context.
Human factors make governance as code a challenge – today we discuss why looking at things like audit and how we determine what has happened and respond to it in an automated way, may be a great first step to adding controls into a system.
We talk about a lot of human factors of what makes it hard to create a governance system, or what creates a biased system or an unevenly governed system.
We spent the first couple minutes of this podcast talking about our agenda, and those conversations spell out a lot of interesting topics that we will discuss. So hang in for those first couple of minutes, and then we will get straight to the governance.