upvote
I think this is a good example. Often each step is easy to explain in terms of previous steps. OK, you've got text. But you want to say where paragraphs are, where headers are, what's emphasized; so you add HTML. Ok, now every time you want to change how one type of thing looks, you have to change it everywhere in the document; so instead you invent CSS -- change the look once, it changes everywhere in the document. OK, so now every time you want to change something, you have to reload the whole page; so you invent AJAX. Ok, now... and so on and so forth. Going from zero to React is nearly impossible; taking things one step at a time makes sense.

Same thing with Kubernetes. OK, so you've got a bunch of servers. But that has problems, so let's to server virtualization. But that has problems, so let's do the cloud. But that has problems, so let's do microservices. But that has problems, so...

And in any case, nobody's going to listen to you explain microservices for 5 minutes and then be able to go actually manage a load of microservices; reality has a surprising amount of detail.

reply
This is why when people ask what I do I change the subject, unless I want them to start looking for someone else to talk to.
reply
When asked about the topic of my main career, I usually say, "I can explain it in 5 minutes if you want", aiming for a tone of "you probably don't want this, but who knows, maybe you do". If asking about one of my obsessions, after the secodn follow-on question, I'll say "I can talk about this literally for hours; so I'll try to answer in short sentences. I'll keep talking as long as you ask questions; whenever you've had enough, just stop asking and we can talk about something else." Because my social circle is full of geeks, many of whom get just as excited about my obsessions as I am.
reply
I usually use construction and maintenance of houses, factories, chemical plants and whatnot as an analogy.

You’re the person that designs and deploys and maintains reusable machines that are used across multiple chemical plants, and if something that seems very small goes wrong the whole factory grinds to a halt.

reply
I don’t know the ins and outs of kubernetes. My takeaway from your description is you help keep complex systems up to date and running, systems people presumably rely on each day and could relate to(?)
reply
Ops here, I just tell my family that I manage rented servers. But what is a server? Well, it's a computer, just more flat, more expensive and more loud. They are located in US somewhere in Virginia.

My family doesn't need an explanation what kube-apiserver is.

reply
Sure, but then you are entirely avoiding the problem of not being able to simplify something complex even if you are an expert - which was my point exactly, i.e. sometimes it just is hard to explain.
reply
You keep the software factory running.
reply