Those can just as easily be screwed up in relational databases. For example getting the schema wrong, or only updating it by accretion (adding new tables). A

Those can just as easily be screwed up in relational databases. For example getting the schema wrong, or only updating it by accretion (adding new tables). A developer being below average (as half of all developers are), using the wrong tool for the job, not understanding things etc will make a mess. A claim that developers can screw things up is uninteresting (and true). A claim that there is no scenario in which a "NoSQL" database is the better solution is a lot more interesting, and requires more than "some developers could screw it up" to substantiate.