It's hard to take seriously an article about how software development is different when it neglects to mention what exactly it is allegedly different from.
Only in relation to one bullet point out of four, requirements gathering.
That particular bullet point is perhaps the most disturbing flaw in the article, I might add. All the projects that I've seen go off the rails are the results of -poor- requirements gathering.
Granted, poor requirements gathering seems to be the rule more than the exception, I have worked on plenty of projects that had excellent requirements that went extremely well, even with the usual set of unexpected scope changes.