logoalt Hacker News

Izmaki • today at 2:28 PM • 5 replies • view on HN

> I think this idea is often misunderstood and used as an excuse by people who don’t want to make any effort to understand a complex concept and want to blame the results of their laziness on the explanation or the explainer.

I agree to some extend. I work in DevOps and even though I've got 10+ years of experience in DevOps, many of those in senior roles, I have a very hard time explaining what it actually is I do, to my family. Take Kubernetes for example: it's an incredibly complex system which requires familiarity with many other complex concepts and theory (e.g., microservices and Continuous Delivery), it cannot be "dumbed down" easily even by those who understand it very well.

I could probably prepare a description of my work to my family which they would understand, but I wouldn't be able to do it on the spot. Not in a meaningful way anyway... "I produce and sometimes invent the automation steps and failure resilience for large numbers of computers and programs to operate" is just as vague as it is accurate, but I highly doubt any of my family members would be any wiser...


Replies

gwd • today at 2:42 PM

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.

➕ show 1 reply
stingraycharles • today at 2:35 PM

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.

jbs789 • today at 2:34 PM

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(?)

mystifyingpoi • today at 2:37 PM

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.

➕ show 1 reply
lovich • today at 2:31 PM

You keep the software factory running.