for writing this profile of me.
If you want to read it, this is your final chance. Tom covers not just my tech career, but my personal journey, and the people behind it.
I never fully understood how far I've come until I read someone else tell my story.
"From McDonald's to Google: How Kelsey Hightower became one of the most respected people in cloud computing" by @tomkrazithttps://protocol.com/kelsey-hightower-google-cloud…
“What people saw me doing with Kubernetes was basically learning in public. I was really excited about the technology because it's attempting to solve a very complex thing.” — Kelsey Hightower (
Back in 2016, I stumbled upon this CLASSIC! https://youtube.com/watch?v=HlAXp0-M6SY…. I'd just moved to the USA from Africa where WinServer is King. My Linux skills were alarming & I'd never heard of K8s. Anyway the rest is history, I'm now the K8s SME at work. Forever thankful
Based on what I know about WASM, and its limitations, which are by design, this is a perfect paring. Given the typical WASM runtime sandbox capabilities, WASM is a good fit for a multi tenant serverless platform.
The Common Gateway Interface enables you to write web applications using any programming language, even bash. Just place your "command" in the right place and it'll be invoked with all the HTTP stuff available through stdin or env vars. This is the OG serverless platform.
I found myself arguing with someone today for no good reason. I've been really good about not doing that. Disagreements are fine, so are debates, but arguing, from a place of anger, or allowing simple discourse to get heated isn't something I see value in.
I'd like some critical feedback on my understanding of Linux containerization, mainly the way tools like Docker do it focused on applications vs something like LXC or even Solaris Zones which focus on running additional OS instances.
I'll yield that OS virtualization is a thing, it's not a term I use because unlike Solaris Zones or IBM's implementations of past, I don't consider what we have in Linux to be on par with that level of isolation.
The problem in the container space is some people treat containers like VMs and package full operating systems as the base layer, shipping around more files and dependencies than they need, while recreating the same security challenges we see in server patch management.
I'd like to hear more about the security part. In my case, container images only package a single statically linked Go binary.
When I package a Lambda function in a zip file or a use a container image with the same bits, I have the same problem in terms of securing the contents.
Yes but when you use a container image you have to still contend with managing the security issues that come with it.
I genuinely don't think this is talked about enough. It's understood, but thought of as a "solved problem" when it isn't.
No matter how complex your application is, it still needs to run somewhere. There are many packaging formats, and 10 times as many platforms to run them on. I doubt there will be one platform to rule them all, so come to terms with all this stuff coexisting.
Lots of people conflate container images, which are used to package and distribute applications, and container runtimes, which unpacks what's inside then hands off to the underlying OS to run.
Applications include serverless functions or code that runs on a WebAssembly runtime.
What was the “celebration restaurant” your family ate at when you were a child that you didn’t realize was not, in fact, a 5-star establishment until you became an adult?
Ours was CiCi’s Pizza.
WebAssembly, like any other application runtime, is designed to run Wasm applications on top of an operating system. How Wasm applications get deployed to an operating system, running on a server, connected to a network, with its specific configuration, is left up to the user.
"Capitalism has always had these two faces - on the one hand, the face of a unique engine of prosperity and innovation, on the other the face of casino capitalism, of speculation and crash." - Political Governance of Capitalism
casino capitalism
Noun
1. A form of capitalism in which large speculative ventures engage in high-risk economic behaviors, especially when they contribute to an economic bust.
“When IDE came along with autocomplete your methods many years ago, it ”
“Bro, we are out of the job” - It didn't happen.
ChatGPT came long - “Wow, we are out of jobs”
I need to start crafting the next job to be more in alignment with where I am. I got to start grinding a little bit smarter. What's the next job that I don't have on call? What's the next job that's going to rely rely on more of my skill than my endurance? 🔥
Join us today for an AMA with one of the most respected engineers in the industry who recently gained the legendary "Distinguished Engineer" title at Google! @kelseyhightower on Twitter spaces https://twitter.com/i/spaces/1kvJpmLywvXxE…
Join us today for an AMA with one of the most respected engineers in the industry who recently gained the legendary "Distinguished Engineer" title at Google!