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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Classifying Software Developers

25 点作者 tkaemming大约 14 年前

2 条评论

lyudmil大约 14 年前
I find the following sentences from the post contradictory:<p>"[Outwardly focused developers] copy and paste code they find in blog posts even if they don’t actually know how it works."<p>"Both [the vocation/avocation and inwardly/outwardly focused] scales are value neutral."<p>I think the first is clearly describing a bad developer. I suspect it is also meant to. There are other such instances in the post, which I fear drains it of content. Sticking with the second scale, it seems to me that when faced with a problem, the appropriate Ruby code ought to be:<p><pre><code> def solve problem my_solution = hypothesize_solution_to(problem) existing_solutions = find_existing_solutions_to(problem) #The sort other is by quality existing_solutions.sort! existing_solutions.reject do |solution| solution.sucks? or my_solution.better_than?(solution) end return existing_solutions.first unless existing_solutions.empty? my_solution end </code></pre> There's some refactoring needed, but the algorithm is correct. I think doing anything different without a <i>very</i> solid reason is irresponsible.
评论 #2504463 未加载
jared314大约 14 年前
I think both this article and the the original article miss the aspect of business awareness. Understanding how the code is used and how it will help someone is a key skill to develop.