The author supports bloated stacks driven by trendy concepts. I highly disagree with nearly every point the author raises. At the end of the day, there is http where there is the request/response cycle, and knowing how the machine works is essential, so obfuscation and nonsense should be eschewed in lieu of greater clarity of understanding. One can pre-load data into a server rendered template but then one essentially has to load new data (hello xhr or websockets) and update the dom accordingly. Everything else is just noise. Full stack engineering gives one a comprehensive overview of the virtual machine. While SPA and serverless architectures (not to mention graphQL, postgrest, and other attempts to basically agglomerate the backend server onto the database) alter this equation, having full comprehensive knowledge of this is the equivalent of a mechanic knowing her/his engine, or a soldier being able to field strip his/her armament.

So, here we have a click-bait title and our reactions are feeding into the apparent pretensions to fame engendered.

next.