[HN Gopher] In 2021, Don't Learn a New Programming Language
       ___________________________________________________________________
        
       In 2021, Don't Learn a New Programming Language
        
       Author : shivaodin
       Score  : 31 points
       Date   : 2021-01-18 14:31 UTC (8 hours ago)
        
 (HTM) web link (sushantsrivastava.substack.com)
 (TXT) w3m dump (sushantsrivastava.substack.com)
        
       | stephen82 wrote:
       | My own concept is rather simpler I would say: apply the 80-20
       | rule; that is, 80% of your time, use the tool set you know best
       | that get you paid and the remainder 20%, invest it in learning
       | things that interest you.
       | 
       | Of course, when it's off or weekend days, feel free to swap the
       | rule to 80% learning and 20% to anything else you must do.
       | 
       | Obviously it's just a suggestion, not a mandatory task, but hey;
       | whatever works for you, isn't that right?
        
         | ricc wrote:
         | What's important at the end of the day is to improve and not
         | stagnate.
        
       | anaerobicover wrote:
       | I've heard the "fox plus hedgehog" idea before, as having a
       | "T-shaped skill set". You have a familiarity with a range of
       | related topics (this is the cap of the T) and deep understanding
       | of a few things (the stem of the T). The premise is that this
       | means you provide valuable expertise (for the deep part). But the
       | breadth of basic knowledge means you are also able to collaborate
       | and delegate well.
       | 
       | I've found that having other languages than my workaday ones in
       | my repertoire is a valuable part of the cap of the T -- although
       | it's certainly not the only kind of thing that should be there.
        
       | crb002 wrote:
       | More concretely learn how to write specs in Gherkin/Cucumber and
       | back them with TLA+ and Alloy before you code. Remember the speed
       | of light (about 1 ns per foot) and annotate those specs with best
       | case data travel latency.
       | 
       | Use holistic profiling like
       | https://twitter.com/OptimyzeCloud/status/1351203905850519557
       | 
       | When you see performance issues then dig into your language stack
       | and learn how to remediate them.
        
       | hankchinaski wrote:
       | unfortunately the tech industry doesnt work this way. i have
       | switched programming languages and this got me to a much better
       | financial and career position. so again it depends
        
       | [deleted]
        
       ___________________________________________________________________
       (page generated 2021-01-18 23:02 UTC)