@jalcine
Not lost. Destroyed intentionally.
@slightlyoff
@braindouche @jalcine So, I was super hesitant to ascribe knowing malfeasance...so much so that it took years for me to come around to it as an even moderately plausible cause. But then I gave this talk in 2016 and a lot of people got upset but the React community changed nothing about their (always wrong) pitch:
@braindouche @jalcine I've prhased this as "lost", in part, because the management class that fundamentally enabled these losses were, in many cases, as dumb as they played. That's not a defense, but it suggests that the malfeasance is extremely narrow in nature.
So when I call folks out now, it's always with an eye towards who I warned 5+ years ago and who, vs. that warning, made changes.
@slightlyoff
That's another thing, that class of managers are the tech bros who staffed their zillion-dollar companies with teams of engineers no older than 27 who worked 36 hours a day. The systematic exploitation of recent college grads in silicon valley has a hell of a lot to do with this.
@jalcine
@slightlyoff
The result, after ten years, is we are stuck idolizing workflows that cannot distinguish between fundamental and incidental complexity, that completely misunderstand the platform they run on, that struggle to reinvent bad wheels better, and prioritize the developer over *everything*. The modern web experience was invented with no adults in the room.
@jalcine
@slightlyoff
It may have been an accidental side effect of valley priorities, but all of front end has been dragged backwards away from systematic maturity by their absolute love affair with jr developer clever codemonkey enthusiasm
@jalcine