I know a lot of the fundamental concepts in computing, many from when they were nearly new. I knew nearly all the concepts long before Windows, 10, 8.1, 8, 7, Vista, XP, 2000, or NT. I didn't learn the concepts in the context of Microsoft or Windows. So, I learned the concepts before I ever saw any Microsoft acronyms.
E.g., I first learned about Kerberos from one of the first papers about it, an article in Scientific American. I learned about RSA and public keys, of course, usable with Kerberos, near the beginning. I still have the source code for an early version of Kerberos. And I learned about and used authentication, capabilities, and access control lists back not too far from their origins in Multics. Sure, later IBM called some of that Resource Access Control Facility (RACF) -- saw some of that, too.
So, at one point Microsoft in Windows Server wanted some authentication, capabilities, with encryption, etc. so borrowed Kerberos and got Active Directory. Fine. So far I've never seen even a single word of Microsoft's Active Directory documentation but likely already understand nearly all the main purposes and core ideas. For working with the actual code, I suspect that I can get the dozen or so operations I need with examples and documentation and, then, be okay on Active Directory.
Uh, in a very significant sense, Microsoft and Windows are an example of the old biology ontogeny recapitulates phylogeny. That is, each organism as it develops from fertilization goes through stages that closely repeat how the species evolved. Well, as Windows grew from Windows 95 to Windows 10, it stayed close to the development of the core ideas in computing, e.g., multiple virtual memory, demand paged, protected, with gate segments, etc., embedded operating systems with an hierarchical file system. They stayed close to the ideas in the Mach kernel. And they are staying close to the ideas in virtual machine. Some of the hardware ideas include instruction caches, data caches, multi-way set associative caches, cache invalidates, page-segment tables, address translation look aside buffers, micro-code, instruction pipelines, speculative execution, out of order execution, parallel execution, etc. I understood all of those well long before I ever touched a PC.
I have a friend with a background a little less than mine who got good with Windows Server, Active Directory, Exchange, running an e-mail server, etc. all fairly quickly. So can I.
There is an issue: I'm trying to be successful with my startup. For that, I need to learn some about computing. Okay. But I'm not trying to be a broadly competent computer professional. The difference is, I just want to know enough for my startup and am not trying to know enough for everything everyone else might encounter. So, a good computer professional can be eager to learn everything in sight (early in my career, I did a lot of that). But as a startup entrepreneur, I want to minimize how much I learn. Significant difference.
Besides, I try to avoid acronyms.