> And poor candidates tend to be poor due to cultural and subject matter issues more than basic technical chops. I wish this were true, but the amount of seemi

> And poor candidates tend to be poor due to cultural and subject matter issues more than basic technical chops. I wish this were true, but the amount of seemingly experienced/employable people I've interviewed in the tech industry who don't understand basic concepts related to their areas of experience/expertise is astounding. As an example I recently interviewed a person to join our operations team managing our VMware stack, who had worked at VMware as an engineer of all places, but could not tell me the difference between paravirtualization and full virtualization or the difference between a virtual machine and a container. More than anything, it seems many people in the tech industry these days lack understanding of the fundamentals. It's great that you've written a RoR app that makes use of APIs, but if you don't know how HTTP works at least at a high level, how can you troubleshoot that API if you encounter an issue? How can you make intelligent decisions about building out the datastore for your system if you don't understand the CAP Theorem, the trade-offs associated with various data storage engines, and the relation between available memory and available IOPS capability and the TPS capabilities of your datastore. People seem to have forgotten the mantra "learn to walk before you run" and have gone straight from being dudebros in high school to being full stack engineers or ops engineers without any time spent actually learning how a computer works. Many of the candidates that we end up interviewing have at least 10 years of experience, and still many fail to understand fundamentals.