TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

In 2021, Don't Learn a New Programming Language

51 点作者 shivaodin超过 4 年前

7 条评论

stephen82超过 4 年前
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.<p>Of course, when it&#x27;s off or weekend days, feel free to swap the rule to 80% learning and 20% to anything else you must do.<p>Obviously it&#x27;s just a suggestion, not a mandatory task, but hey; whatever works for you, isn&#x27;t that right?
评论 #25827288 未加载
amw-zero超过 4 年前
This wasn’t what I expected, the bit about formal specification languages was really (pleasantly) surprising. I happen to have been spending a ton of time recently writing TLA+ and Alloy as the author mentioned. It’s completely changed my perspective on testing, definitely.<p>But the really surprising thing is how much they affected how I think about software overall. You know, at work I’m busy trying to build things. But taking a step back to understand what computation really is has been so helpful for even the code I’m writing on a daily basis.<p>Specifically with Alloy, which has an awesome state viewer, you can use it as a tool for prototyping ideas really quickly. It does suck that you can’t take that and use it to test your actual code, but I have ideas there :)<p>Anyway, yea I can’t recommend those tools enough. I think specification will grow in popularity soon - and no that doesn’t mean specifying your whole program up front. It’s totally possible to spec a program out iteratively. The value is huge - we write user stories and have product docs somewhere which explain what it is we’re building, but they get completely discarded after building. Having a highly simplified description of what a piece of software is expected to do is invaluable, especially as members come and go on the team. Agreed. In 2021, we don’t need another programming language. We need to master the tools and processes that we have.
anaerobicover超过 4 年前
I&#x27;ve heard the &quot;fox plus hedgehog&quot; idea before, as having a &quot;T-shaped skill set&quot;. 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.<p>I&#x27;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&#x27;s certainly not the only kind of thing that should be there.
评论 #25829401 未加载
pdimitar超过 4 年前
Learn stuff when it makes sense.<p>Two and a half years ago I felt stuck working with only dynamic languages most of my career so I started learning Rust. Now I have an extremely powerful tool in my belt that solves problems that most dynamic languages cannot solve [adequately].<p>But I&#x27;m not going to learn yet another dynamic language if that won&#x27;t make me any money or expose me to a new way of thinking, no. Nor will I relearn C++.<p>Furthermore, if I make a comeback to JS then I&#x27;ll prefer to learn TypeScript and pick the most productive tools for it (Parcel struck me as mostly getting out of the way).<p>I get the overall sentiment of the article even if it expresses it rather poorly.<p>It has a good point, though; many of us the programmers are rather capricious and spoiled and get distracted by new shinies -- as opposed to learning several skills deeply and be then very useful to the business we&#x27;re serving.<p>We easily forget that we do what we do for money.
评论 #25829387 未加载
hankchinaski超过 4 年前
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
kingsleyopara超过 4 年前
I&#x27;d planned on learning Rust this year, this article did little to convince me otherwise.
评论 #25828708 未加载
crb002超过 4 年前
More concretely learn how to write specs in Gherkin&#x2F;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.<p>Use holistic profiling like <a href="https:&#x2F;&#x2F;twitter.com&#x2F;OptimyzeCloud&#x2F;status&#x2F;1351203905850519557" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;OptimyzeCloud&#x2F;status&#x2F;1351203905850519557</a><p>When you see performance issues then dig into your language stack and learn how to remediate them.