Kettle, pot. In recent decades, UX has been coopted and corrupted to the point it's no longer about the user experience, it's about how best to manipulate user

Kettle, pot. In recent decades, UX has been coopted and corrupted to the point it's no longer about the user experience, it's about how best to manipulate users into doing things that will improve our growth metrics. I agree in principle with the article, and have seen first-hand what agile[tm] can look like. However, the tone comes off as condescending (the snarky agile manifestion translations don't help) and the conclusions come off as incredibly naive: "Determine what to build, determine how best to build it, invest in foundations and do operations the right way"? Gosh darn, that sounds so simple, why didn't I think of that earlier?!