Lets look at it from an evolution of technology angle.<p>10-15 years ago we had pain points with web apps and making them more fully featured&#x2F;responsive and dealing with things breaking at scale. They were kind of clunky to build so, we did what all good engineers do and figured out how to make things easier to use for everyone. Now a days, the &quot;kids&quot; are learning how to build web apps that don&#x27;t require a deep level of knowledge about the stack - we&#x27;ve done a fantastic job building out the tooling that abstracts a lot of these concerns away from the &quot;average&quot; developer. They know if I install framework X and use Library Y the two will communicate correctly. I might understand how they communicate, but don&#x27;t need to know the intricacies at this time.<p>Technology is always evolving and what you need to know at a deep level is changing. 
60s&#x2F;70s&#x2F;80s - The size of the program, how it was laid out on disk, disk sectors, memory layout. All that mattered to get the best performance. You needed to understand how the hardware worked intimately.<p>90s&#x2F; early 00s- Managed languages (Java etc.) become more of a thing and you need to understand less about all the gotchas the prior generations faced. The framework and language abstracted a lot of the prior generation&#x27;s challenges away and increases in hardware capacity reduced the need to layout programs just so on the disk or in RAM.<p>Early 00s-Present - Hardware kept growing exponentially in terms of capacity and performance, and we started placing more emphasis on building out scalable, fully functioning web applications (thin clients) rather than thick clients running on a desktop. People figured out a lot of these applications were simply wrappers about DATABASE activities and wrote frameworks that made writing the backend for such apps KISS simple. RoR I&#x27;m looking at you! This freed up people to focus on the bells and whistles the user interacted with and reduced the need for anyone developer to know the intimate details of how their framework worked.<p>It&#x27;s a changing world and the next generation of programmers is always going to be starting at our current level of abstraction, much like we started at our prior generation&#x27;s and built our way up. Challenges we faced, overcame, and turned into libraries, become the starting assumption for the new kids that they&#x27;ll build up from.<p>On the flip side, I gotta ask, what are you looking for? There are so many &quot;full stack&quot; combinations (language, server, SQL&#x2F;NoSQL database, front end scripting library) now that the odds of finding a person with deep experience using everything you are using, unless you&#x27;ve reduced to the lowest possible common denominator, is low. Are you looking for someone you can train into the position and has enough knowledge not to blow their foot off, or do you want someone who you can plugin ready to go? Your expectations will influence how you&#x27;re viewing the candidates, your expectations, and your relative measure of disappointment in them.