>Not really. That is exactly the point the article is trying to make. Developers need to care about these things - _enough to know who to go get help from_. Th

>Not really. That is exactly the point the article is trying to make. Developers need to care about these things - _enough to know who to go get help from_. That isn't it. They aren't telling you to learn about database details for the sole purpose of "DBA handles databases. Go ask the DBA database questions". It's more than that. They're offloading specific knowledge onto the dev and then making them accountable for it. It's a reaction to common questions and an attempt to answer them all at once by teaching devs answers to common questions. This is a noble goal, but it's problematic in aggregate from multiple perspectives. The aggregate goal of all of these areas trying to teach developers their own specialties is to make developers the masters of low-hanging fruit.