The whole post, and both the Twitter messages sound like they refer to a very specific style of work.

These things "sound good but almost never work" when they're taken as an afterthought or committed to without due research/process/design.

Any architect worth their salt will avoid implementing hard solutions to these problems. These are mostly here to not solve crucial issues... but the article seems to be addressing a developer profile that adds APIs or asynchronous processing casually.

Sounds like a strawman, or just exceedingly pessimistic look at the industry.