When they said that it wouldn’t be a “get off my lawn” post, I was like “oh no, it’s 100% going to be that”, but then I read, sympathised and… I’d actually offer to get the people in the examples off the author’s lawn on their behalf, because they were just so disappointing.

Though, to be fair, this was pretty much a problem in the superficiality of the frontend development circle that maybe was taught just that from the beginning, so they conflate notions of computer science with the language they use most, because there was no formality in their approach to learning, which is sort of a good thing IMO, because it’s way more effective at making you productive fast and knowing where to put your hands. Just that, after that, one shouldn’t pretend to have the understanding necessary to pronounce on topics they actually haven’t dug into, they, as I, and anyone for that matter, should delve into them first to know what they’ll be talking about.
What the author identifies as “developer disconnect” I think is ultimately a product of the popularisation of coding beyond the academic setting, when you learn on your own, you can have several holes at the base of your knowledge, holes that would be glaring to someone that took a more standard path to learning, but that weren’t limiting enough to impede their advancement and that is hardly ever addressable, because still, when you’re on your own, you have the (blessed) choice to skip everything you don’t care about, until you need it at least, if you ever do