Why can't it be both?
I'm not one to give engineers a pass on this sort of thing; indeed, I consider making a serious attempt to understand something completely before using it to build products to be one of those modest professional nuances that distinguishes engineers from devs (and goldfish). At the same time, Adobe failed to demonstrate another modest professional nuance first by creating a template or demo that does not reflect best practices, then by shipping it without noticing the problems, and finally by recommending that a configuration template from a demo be used by customers instead of creating their own from scratch after reading the (hopefully) complete documentation, providing a tool to create one that will be correct by default, or any other safe approach.
That there are undoubtedly thousands of customers who are going to copy-pasta out of demos or stackexchange regardless does not excuse any of Adobe's errors. This is a classic example of multiple things going wrong to cause an eventual production failure. Correcting any one of them would have prevented the ultimate failure. The author of a piece of software puts his or her name or brand on it and assumes responsibility for its content regardless of who else made various components. When they did so, both Adobe and its customers failed in their duty to their respective customers. But engineering is passé; everyone wants devs now because copy-pasta gets you to market faster. Deploy to production from your desktop, move fast, break shit, disrupt. Devops! Agile! We don't have time to understand what we're doing or why. And you can see that mentality at work on all sides in this case. No reason to choose just one! If you really don't like it, stop giving these people money.