> That seems to misunderstand the path from apprentice to journeyman (singular) to master That or this? And I don't believe it does. Also no, "actual" engineer

> That seems to misunderstand the path from apprentice to journeyman (singular) to master That or this? And I don't believe it does. Also no, "actual" engineers don't still (universally) operate in a master/apprentice model. I've heard of that happening in quite some time. > Look to actual (not software) engineers for that. This is putting down software engineers who are, by definition of engineering solutions, real engineers. They're just simply not in regulated markets. > There is also a deep misunderstanding of what the Internet is. It's not a "third dimension" or a set of marketing hype. It is an engineering marvel. Which part of the article said the Internet was a marketing hype? I think you may have taken the term "third dimension" a bit too literally here. The author didn't mean what you thought they meant. > This "pyramid of mastery" is roughly as sensible as organizing your bookshelf by color. Networking fundamentals come before learning to use AWS VPC peering or VPNs, which are tools and frameworks. You learn one before you learn the other. I think the structure is valid. EDIT: Apologies for being so crude in my original wording. I'm updating the comment to reflect a more professional, civil tone.