While I try to stay technical and current on topics and solutions, many times, I have engineers or friends who are intimidated by a new construct. All have their own terminology and buzz words, and if you hope to use context clues in conversation to ascertain their meanings, you are much more likely to end up confused.
For myself, I am a person who will put an address into my GPS to find a destination. I can (and do) continue to use the address and GPS to return multiple times. However, if I never venture into the wider area and learn where this particular address is, in the context of every other place that I know in the area, I will never be able to return to that address without the GPS. It does not matter how many times I have been there. That is just a fact about how my brain works. Those who know me, know that I explain my path to understanding this way.
The same is true for me in learning new concepts in technology. Many times, I will not even realize that my mind has made some subconscious assumption until it is questioned, and then a light bulb will go off, and the gray-area dots connect. (Don't get me started on M365, on-prem AD, Azure AD, and Exchange.)
What I have found is the adage is almost always true: "What is old is new again." This is a great thing for me, as this is the open secret of picking up new concepts quickly and explain them to others.
All of that is purely a preface to say that, at times, the easiest way to make these connections is a cute little cheat sheet. In this case, one was made for Kubernetes last year. I found it in a OneDrive purge and decided to share it here.
So, for those of us who grew up with Microsoft and/or desktop development —yes, BEFORE the internet took over —I have taken some terminology from today and related the phrases to concepts from the deep recesses of our brains.
Anyone who happens upon this, please comment to correct anything that may have evolved since its inception.
Comments