But data-oriented design usually does result in much simpler designs, readable code, smaller architectures, and easier composition. What it doesn't do is let s

But data-oriented design usually does result in much simpler designs, readable code, smaller architectures, and easier composition. What it doesn't do is let some bootcamper pick up some A-B-C-D-E pipeline (whether that's literally some report generation pipeline, or an HTTP ingress to a CRUD DB, or whatever) and plan their whole career around (some subset of) just B. Or let some serial entrepreneur cycle through a cadre of these guys as he burns them out in turn, because to pick the right choices for B you need to understand (and be able to influence the design esp. re. data representations in) A and E. Nothing actually lets you do that and still produce good software, and we should stop pretending otherwise.