Even the truth in the original demonstrates ignorance: front-end (and client-side generally) has layers to occupy you for multiple careers!
Codecs, databases & storage, graphics (2d & 3d), languages & runtimes, fonts & layout, networking, performance: all harder on the client.
Codecs, databases & storage, graphics (2d & 3d), languages & runtimes, fonts & layout, networking, performance: all harder on the client.
https://twitter.com/padolsey/status/1341851590039318529
It *is true* that working across layers is a key trait of highly effective engineers. Respecting those who do it on the client is good.
The idea that one must "graduate" to the back end carries the same stench as every overconfidently presented "full stack" failure I trace.
The idea that one must "graduate" to the back end carries the same stench as every overconfidently presented "full stack" failure I trace.
Front-end demands humility because it is *different* and, in key respects, *harder*.
There's an asymmetric hubris here: those of us who work the client don't tell back-enders that their work is trivial. Nor do we gate-keep the "full stack" crowd, no matter how poorly they do.
There's an asymmetric hubris here: those of us who work the client don't tell back-enders that their work is trivial. Nor do we gate-keep the "full stack" crowd, no matter how poorly they do.
If only we could just not render webpages for the huge amount of the industry that can't be bothered to respect how hard it is to put pixels on screen at 60fps, sipped through a network straw, on computers you don't own and can't control the software of.
Not in a malign way, ofc. They could earn use of browsers back, layer by layer, explaining in high fidelity how they work, starting, idk, with a passable description of 3G's CDMA/TDMA tradeoffs? Or maybe a good description of TLS and PKI? Either would be fine. We're not monsters.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
