I think that without a lengthy disclaimer the author is misrepresenting his opinion to novices as being some sort of guide where you can choose your path from level 0 to 1 to 2 for rows in the table and that somehow you will become a good programmer. This is evidenced by the comments section with one user asking to "tell us a roadmap or path using which a programmer can advance his skills from Level to Level 2 and from Level 2 to Level 3."
To cherry-pick an example that helps my argument, how does having a blog remotely affect my ability to ship good code that is on-time and within budget? Why are Erlang and Prolog considered to be level 3 languages when they are not suited for all tasks (in fact languages are but a tool that should be chosen appropriately for the task)? Why must I author a framework to reach level 3?
The more I look at that table the more it disturbs me in it's subjectivity but is nonetheless an excellent resource for starting the discussion on what skills should be considered relevant for one's career.
To cherry-pick an example that helps my argument, how does having a blog remotely affect my ability to ship good code that is on-time and within budget? Why are Erlang and Prolog considered to be level 3 languages when they are not suited for all tasks (in fact languages are but a tool that should be chosen appropriately for the task)? Why must I author a framework to reach level 3?
The more I look at that table the more it disturbs me in it's subjectivity but is nonetheless an excellent resource for starting the discussion on what skills should be considered relevant for one's career.