Communication is difficult, but isn't the hardest thing, just another in a long list of difficult things. And requirements aren't hard because of communication

Communication is difficult, but isn't the hardest thing, just another in a long list of difficult things. And requirements aren't hard because of communication, requirements are hard because they are mostly unknown to everyone involved. While there are "little r" requirements in projects, if I encounter a group/firm/company/culture that puts a capital "R" on the word, I try to stay away. Creating software is largely finding something worth creating, and a process that puts Requirements in the foreground has an implicit assumption that Waterfall actually works. The essay starts off on the wrong foot and doesn't really go anywhere that hasn't been trodden in countless other articles. Even worse, it ends with "no/low code tools will save us!"