Read in context. He's referring to the evolution of skill at group level, he even puts out the definition of deskilling and mentions 'skilled labor'. He then explains how frontend used to be a 'highly specialized skill', and how modern devs use Frameworks to consider browsers almost hidden compilation targets.
replyThe article explains at length what they mean by "deskilling" and it does not mean that individuals lose their skills.
replyThe author having worked with various technologies over time is also not an example of "deskilling", it's a way of asserting that they have had time to observe the deskilling of the domain (since deskilling means a particular domain requires less specialised skills than it did before, not that the workers are losing skills) happen.
The phenomenon of bootcamp graduates who knew React but did not know JavaScript.
replyyes and now they get Claude to write React and don't know that or JavaScript.
replyWhen something goes wrong, no one understands anything.
I guess the author never tried to write big FE application in jQuery :D It definitely required some skill.
replyJust watch the terrible soup produced by MIT-bred Leetcode ninja "engineers" in money raining startups and FAANGs.
replyLow accessibility, terrible performance, lack of any fundamentals of html and css, abuse of those awful solutions like Tailwind or using 2016 technologies like React for rendering what should mostly be static websites + some web component, all plagued by memory leaks and very basic usability bugs.
[dead]
reply