|
|
|
|
|
by swyx
525 days ago
|
|
i mostly agree w you, but theres a wide spectrum of “understand the inner workings” given rising complexity. consider: - does a React/frotnend engineer need to know everything about react internals to be good at their job? - does a commercial airline pilot need to know every single subsystem in order to do their job? - do you, a sophisticated hackernewsian, really know how your computer works? more knowledge is always (usually) better but as a thing diffuses into practice and industry theres a natural stopping point that “technician” level people reach that is still valuable to society bc of relative talent supply and demand. |
|
Yes? Well, not everything (which I define as being able to implement React from scratch). But if you want to do good work, and be able to fix those pesky bugs which result from the arcane behavior of the framework itself, then you better know your stuff.
Besides, in practice very few people understand the most basic stuff about React. Just recently I had to explain to a veteran frontend dev what list virtualization was and why it's not a good idea to display a list of 100k items directly.