How do we design a deliberate culture in today's environment? And what does a deliberate culture look like?

Yeah, I mean, it's something I obsess about, right? I tend to think of culture as the operating system of a team.

And a lot of people are kind of dismissive of this nominal idea of culture.

It's the thing that HR writes on the sheet, and there's five points on a poster and a bunch of people jumping with their hands in the air, and it's plastered all over the hallways, right? That's not culture.

Culture is the operating system of a team.

It defines how the team process information and it is intended to establish a set of commonalities.

I truly believe the best teams have very high levels of diversity.

What's your advice for the reasonably new team lead, technical lead, looking at how do they support their teams and looking to the future?

But, but say more about what you're hearing from customers, that problem, and, and how you think about the framework to go, uh, best address it.

I think there's a lot to unpack there, but, I mean, the way I would start with it is, you know, uh, I think we're starting to see a hint of what the future looks like for knowledge workers through the lens of developers.

What I mean by that is, if you look at the way that a modern development team operates right now, you look at the way that the StackLock development team operates, we are generating tremendous value through the use of agents, and the way that we work has changed.

It's no longer a single developer operating in an IDE.

It's a single developer taking responsibility for the work product of a pretty broad cross-section of agents that are all specialized to perform certain tasks, and the developer is really becoming the center of orchestration for these, these agentic systems, curating them, making sure that they can un-understand the work product that's being produced, being accountable for their behavior, and ultimately making sure that they're, they're, they're productively engaged in a direction that the company cares about.

And so when we think about, you know, where this is going over the next few years, I think, you know, what we're seeing in the development space will naturally start to cascade into the knowledge worker space.

But there's gonna be a lot of challenges for knowledge workers to be able to embrace that, that, that pattern of, of engagement.

But like, where to start? So from just, like a user adoption standpoint, do you see patterns within your, your customers about where, you know, where they're most focused initially?

So, Craig, what's your origin story? What's your background story?

All right.

Well, I don't know if I'm a superhero, but I'm happy to share my origin story.

I'm an enterprise technologist.

I've been building platforms for probably the best part of 25 years.

I came from South Africa, got a job at Microsoft.

And then I guess my story got really interesting when I had a chance to go work at Google.

A lot, yeah.

Mm-hmm.

You know, I think this is probably...

You know, it's funny, my, my buddy Joe, who I've worked with for years, like, you know, we built from Compute Engine together and Kubernetes and Heptio and Tanzu, and like now he's my CTO here at, um, at StackLock.

He wrote the SPIFFE paper.

I don't know if you've heard of SPIFFE.

It's, it's an identity system that's kind of, uh, a sort of, the sort of zero trust, you know, kind of identity framework.

And, uh, he wrote that paper about 10 years ago.

Um, and as we are kinda taking the concepts that you're sharing with us and, and diving into how you guys are approaching, you know, the, the proxy issues and stuff, could you, could you, uh, for those who haven't, uh, had any exposure to Tool Hive, could you, could you take us into what that is as a, as a solution, um, and kinda define how it fits in with some of the, the context that you just now addressed? That'd be fantastic.