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.
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.