Title: Hi HN,<p>Very recently I stumbled onto a comment by Rich Hickey which I&#x27;ve reformatted in a gist[0] (unfortunately, the source is no longer available). Honestly, Rich Hickey is one of my programming heros and I&#x27;m a big fan of his ideas about programming. However, reading the response below, I couldn&#x27;t help but feel disheartened.<p>Rich Hickey says - <i>You don&#x27;t level up by switching games all the time, but by sticking with one long enough to gain advanced skills. And, you need to be careful to recognize the actual game involved. Programming mastery has little to do with languages, paradigms, platforms, building blocks, open source, conferences etc</i>.<p>Quite seriously, this is more or less opposite of what I&#x27;ve lived by in my career till now. As a backend engineer I can&#x27;t help not getting excited by React or not spending a month learning OCaml or building side-projects tangential to my 9-5 line of work. The worst part is, that till now I always felt that it is a sure fire way to level up as a developer.<p>The confusing part is that Peter Norvig, another great programmer has quite the opposite to say[1] (although one can argue that overall they mean the same) - <i>Learn at least a half dozen programming languages. Include one language that emphasizes class abstractions (like Java or C++), one that emphasizes functional abstraction (like Lisp or ML or Haskell), one that supports declarative specifications (like Prolog or C++ templates), and one that emphasizes parallelism (like Clojure or Go).</i><p>At this point, I&#x27;m really confused and I spent better part of the day mulling over whether I should go through the lectures of a recent Coursera course that I&#x27;m doing or should I dive deeper in my current stack e.g. Python &#x2F; Django.<p>What are your thoughts? Is there one school of thought that you agree to?<p>[0] - https:&#x2F;&#x2F;gist.github.com&#x2F;prakhar1989&#x2F;1b0a2c9849b2e1e912fb
[1] - http:&#x2F;&#x2F;norvig.com&#x2F;21-days.html
Upvote: