Classifying Software Developers

I find the following sentences from the post contradictory:

"[Outwardly focused developers] copy and paste code they find in blog posts even if they don’t actually know how it works."

"Both [the vocation/avocation and inwardly/outwardly focused] scales are value neutral."

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:

  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

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.