An article like this is the sort of thing the developer with the least interpersonal skills drops into Slack the day after someone's presented a transformation plan that has been researched, vetted, piloted, and roadmapped because they don't want something to change, and they didn't read the top two paragraphs before scrolling down to the part with all the capital letters. Good on the author for helping that person remove all doubt.