I don't read it as "say no to databases," but "stop putting square pegs in round holes." Too many programmers find a Next Greatest Thing and then try to reconf

I don't read it as "say no to databases," but "stop putting square pegs in round holes." Too many programmers find a Next Greatest Thing and then try to reconfigure problems to fit the newfound solution. Too many managers "need" solutions that are buzzword-compliant. Combine these and you get projects that are "written in C++ and use databases" and are thus a success regardless of whether they work.