Career Advice Part 2

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.

PART 1: the2030.cloud/2022/06/19/the-car…e-wish-wed-gotten/

Image: www.pexels.com/photo/person-s-ha…hing-wall-626163/
Transcript: otter.ai/u/t2JEhT0XXcbPvDVuDM-OTRP_G84

The Dangers of Interconnected Systems

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.

Transcript: otter.ai/u/6m6yPHG7cV_lrmdOEPGyHmo1ifM
Image: www.pexels.com/photo/men-pulling…n-a-rope-7678454/

Events And Monitoring [bonus Complexity chat]

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!

Image: www.pexels.com/photo/green-and-b…ug-on-air-905905/
Transcript: otter.ai/u/udK3y3upQMszo2IVtbrdGigmehE

Humans vs Code: Governance As Code

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.

Transcript: otter.ai/u/aqx5-wivDgPARqAXwXGCIm-bO5U
Image: www.pexels.com/photo/belgium-fla…-building-532864/

Real Life Chaos Monkeys And Other Infrastructure Challenges

How do we use chaos monkeys in real life, and practically? This happens all the time when we have failures. The Rogers failure that took out the internet and cell phone use in Canada last week was the start of our discussion.

Predicting how things are going to go out is a common theme for chaos monkeys, and really comes back to how we test infrastructure. Should we be putting it under stress in planned ways like Chaos Monkey, in order to ensure that our increasingly internet and power dependent society is prepared for the inevitable outages?

We have a really fascinating discussion about what it would take to make this type of practice real, including alternatives that people can look at today.

Transcript: otter.ai/u/D0ZV5c3ikvAiinsK7ugf_duCjv8
Image: www.pexels.com/photo/monkey-sitt…s-hands-11999152/

Defending Against Complexity With Exercise

How do you manage complexity? Something we talk about a lot in Cloud2030 is how challenging it is to understand complexity, measure it and cope with it.

Richard Cooke wrote a paper called “How Complex Systems Fail,” (how.complexsystems.fail) and in it he talks about complex systems having strong defense mechanisms against failure. That’s what we talked about today. How do we build defense mechanisms for complex systems, not by making them simpler, but by exercising them and testing them?

We discuss the importance of testing, validation, and layer of abstraction and testing the layers in this conversation. If you deal with complex systems, this discussion will be fascinating and actionable.

Transcript: otter.ai/u/SP-z7OAJWAmJlql8Dh62rNk2hlo
Image: www.pexels.com/photo/man-woman-m…ng-young-4058411/

Why Jenkins in DevOps?

What kind of orchestration systems does the industry use for infrastructure, automation and controlling day to day operations?

In today’s episode, we talk about infrastructure pipelines at the tooling level, and specifically the use of Jenkins and other CI pipelining tools for ops and orchestration. We dig into why and how you would do this, and what pieces are missing from the system. That conversation leads us into larger day to day challenges.

If you are doing infrastructure ops and DevOps automation, you will get a lot out of this session.

Transcript: otter.ai/u/dbTdHdYTIt5bU1G8SFghKSijhU0
Image: www.pexels.com/photo/barista-wit…d-tattoo-6205639/

Green Data Centers

What’s going on with green data centers, why does it matter, and how do we think about it in a wider context? In this short conversation, we discuss green data centers and creating carbon neutral infrastructure.

This isn’t just about servers using electrons – the actual conversation about making our infrastructure carbon neutral includes thinking about all of the components that go into our infrastructure.

We also have an upcoming series of conversations on green data centers and carbon neutral infrastructure.

Transcript: otter.ai/u/IYsPlr4r570MmOOW3WWLjenDlWk
Image: www.pexels.com/photo/clear-light…ray-rock-1108572/

OSS, Promotions, and Lava Lamps

How can promotion boards be hostile or hurtful to open source technology? We talk about the dynamics of corporate support in open source technology, and if being rewarded for internal work at companies translates into challenges for open source technology.

This discussion starts to peel apart what makes open source technology sustainable, and what it works for. We bring up an analogy of a lava lamp where things heat up and then cool down as part of a natural cycle, which can be a normal cycle for all software, and that led us back to how promotion boards work.

We covered a lot of ground through the dynamics of corporate software governance and open source and interweaving those together.

Transcript: otter.ai/u/nZS6rtcam88JUuqMctOiEyWq5G4
Image: www.pexels.com/photo/food-cold-d…nk-glass-5677999/

APIs With Composable State

What makes API’s complex? In this episode, we talk about how we compose APIs into higher level systems, and how we think about the design elements that go into building durable, reusable API’s.

This is a classic topic for us, and in this discussion we looked beyond the API itself and started talking about the state of the system and how you manage that state.

Transcript: otter.ai/u/Oae5e_ay0d_l48TmWk3PO3lpIDU
Image: www.pexels.com/photo/a-nacho-chi…ng-sauce-5848731/