Kelsey Hightower

There you go.

That's how you do it.

And I was like, yeah, I mean, of course you have to prepare, of course.

And so the question then was, from an engineering perspective, how will we make this better?

And then people were like, well, if we had OS packages, this could have been avgit install, and we could have just used local machine.

It's like, that's a good idea.

And someone was like, we will make that happen.

Another person's like, even if you have those packages, though, you still need to know what order and where the config files go.

So KubeAdmin was born, which was a command line tool that gave you a procedural thing.

But the other thing that I remember from my career was, I don't want just a tool that abstracts everything from me.

I want to know how it works.

So I wrote the guide, Kubernetes the Hard Way.

And that guide is what I used to help teach people at GitHub in the early days, pre-Microsoft, how to run Kubernetes on bare metal and walk them through that guide.

And so it was that empathetic engineering that helped me make a huge impact on cloud because I can go to every team, every org, and instead of guessing what their roadmap should be, given someone who would spend time in the field, given someone that had this enterprise background, hands-on experience across lots of tooling, I knew where people were coming from, I would say, based on where Google sits in the landscape and in the competitive landscape, given what our abilities are and what our customers need,

I think this is it.

But I never said it that way.

I would get everyone in the room.

I tried to always know the two things in multiple product areas that would make the most impact, aka revenue, that would get adoption.

And then launches versus landings.

You would put all these things in motion.