4 ms·
“True mastery, true depth” is impossible in our field. If anyone disagrees, find me someone with mastery of the 10 latest JavaScript frameworks, or whatever ser
by booleandilemma 8y ago
“True mastery, true depth” is impossible in our field. If anyone disagrees, find me someone with mastery of the 10 latest JavaScript frameworks, or whatever service Amazon put on AWS last week.
What you what is someone with a strong knowledge of fundamentals, everything else follows from that.
- harshalizee 8y agoI think that's exactly what 'true mastery; true depth' would mean. People with incredibly strong fundamentals can look past the fancy facade of a new framework/tool and deduce its possibilities and limitations quickly enough.
- strken 8y agoIt's probably possible to have something approaching true mastery over compilers or physics simulation or distributed databases, or anything that's a field instead of a framework. Asking for mastery over React instead of over UI engineering is a little like asking for deep knowledge of Torx screwdrivers - there are high level concepts from internationalisation, accessibility, QA, automated testing, and UX design that will still apply in a decade or two, even if we write all our UI code in Rust and steam lightweight VDOM diffs to the server or whatever.
- jdbernard 8y agoIn the video Randy addresses this very point. In his delivery #1 and #2 are actually part of the same point. He explains that true mastery of something, even unrelated, shows the mindset needed to dig in to a hard problem that's never been solved before. That leads into the discussion of failure and the persistence required to overcome failure and reach mastery. Not too far away from your advice regarding fundamentals.