Can someone remind me how we ended up in the SPA era and why exactly? Was it about not seeing the loading spinner? Or there were more reasons to it?
I'm not in web anymore but, to me, it seemed easier to visualize richly linked data in Angular than having a Django template render it. Once you have the mindset of making your website into an app, you are tempted to move navigation to the app too. That way your app can keep delivering its core user function without the interruption of a page load.
In retrospect it was slightly hubristic, as in reality you sometimes have to force reload SPA's, and if you're integrating on top of legacy systems that you just link to, you're not really avoiding the bad UX of a jarring page load. But I do find it elegant to separate presentation from data.
Every sentence is separated into its own paragraph, like each one is supposed to be revelatory (or maybe tweet-worthy). It's pretty common design knowledge that if you try to emphasize everything, you end up emphasizing nothing. The result is that reading the article feels choppy, and weirdly unsatisfying, since the larger arc of each point is constantly being interrupted.
Why choose such an antithetical form, to what is otherwise an important and deep message?
The only answer that comes to mind is that the author's livelihood, or at least their internal gauge of success, is tied to manipulating readers' thin desires.