I don't want to defend the author's point, but I do believe he saw this happen, because I've seen it myself. People used their IDE for something like code generation, didn't know how to do it without the IDE (even positively said it couldn't be done outside their IDE) and then when a database column gets added and somebody with a different IDE tries to tackle the problem, they can't. "I can tell you how to do it with Eclipse." "I... haven't used Eclipse since 2007." "Well, after you install Eclipse, here are the directions for setting up the plugin and regenerating the database code."

To the author's statement that it affects adoption of CI/CD, I've seen that, too, where teams didn't know how to run their Junit unit tests outside of an IDE and nobody felt capable of figuring it out. They were wrong, it didn't take too long to figure out, but they honestly believed that running Junit tests was a feature of their IDE, and were not aware that it could be run separately.

These aren't persuasive arguments about using IDEs, because any sensible person can avoid them. I don't want to defend the author's point; I just want to say that I believe him when he says he's seen these things.