I get where a lot of commenters are coming from, abstractions are good. I work in them.

But I also rage quite my last job because the company let their half-billion dollar system crash for the better part of a week despite numerous warnings about issues in their threading. They didn't understand the problem, not even the other engineers in the company, and didn't believe it would happen until it did.

That was the straw that broke the camel's back.

I will not even work with javascript devs again, they've proven they don't have two braincells to rub together at every company I've ever worked with.

Thing is, most developers getting into the field today are in it for the money. If you're surrounded by those, leave. It's fine not to know everything, it's perfectly acceptable to rely on the magic of abstraction for your day to day work. It's unacceptable to know nothing about your architecture beyond your one little corner. Any dev who thinks that's okay on my team is out the door pretty quickly.

I do my best to ensure cross-training occurs, especially between development and devops, but some people just don't want to learn. Not even on company time.