>so we're back to point one, you need devs that go trough basic education There is no basic education that covers the associated costs of a TCP connection in t

>so we're back to point one, you need devs that go trough basic education There is no basic education that covers the associated costs of a TCP connection in the kernel of a modern operating system or in the load balancers it passes through on the edge of the network. >sure but it is knowable So you're saying it is important for a developer to understand the infrastructure the code will run on. Thank you The reason I brought up all of those points is because they are things not covered in CS educations and they hammer "hands off" devs all of the time. I've worked with tons of junior devs from all kinds of good schools (Stanford, MIT, UC Berkeley, etc) and they almost always get bitten by this stuff because they throw their code over the wall and don't make an effort to understand the operational environment. It has nothing to do with a good education, it has to do with a mindset of not operating in a vacuum.