Do not fall into the error of the artisan who boasts of twenty years experience in his craft while in fact he has had only one year of experience — twenty times.
Most probably Trevanian has drawn upon some other source, tough I've never been able to track that.
If you haven't read this fantastic book I strongly recommend it.
It's also impossibly incorrect politically -- so transparently so that I think it's essentially harmless. But if you don't understand why some people would feel that why you really should watch your step.
But the rest… I assume it's a matrix for a reason. Someone isn't a level log(n) programming mage, but he or she might be a level log(n) data structure and algorithm wielder, a level n^2 systems programming apprentice, and a level n requirements gatherer, or some other combination of strengths and weaknesses. It's still a lossy abstraction, but significantly less so taken that way.
Everyone in the programming world knows programmers (often intelligent, educated, and experienced ones) get caught up in silly details of perfecting their code and are completely unproductive without an experienced manager (or tutor) guiding them. I can't help but laugh when a bushy tailed non-programmer steps in, and produces something quickly and effectively using seemly simple tools.
I'm ~40 and going back for a CS degree isn't very appealing / practical. But if I knew what things to study... I could start on my own.
I'm advanced in my career, but its been mostly advanced level support and system administration work. I want to get into programming.
I say all that to make the point that a degree track isn't the best fit for me.
The side projects don't even have to lead anywhere, but they get you to the point where you can say "ya, I can write a node.js server" and then you can do it on the job, and a few years later you're an expert.
This is definitely not the only way to acquire skills. I'm sure some people dig through books, or just focus on doing their job and still grow. But for me, side projects have always been the driving force.
You can also always program on the side if you want to maintain the stability of an established career.
I can't help thinking when I read these lists, though, that they probably favor the author's particular skill-set and experience. Maybe not necessarily the author's current state, but perhaps where they'd like to go or what skills they aspire to have.
Some people I know are great at fixing bugs but have narrow language experience. They're damn valuable. Others integrate well into teams and provide great product feedback. Where's that on here?
Experience isn't measured in years but in knowledge gained. You really start seeing it 4-5 years in, some people move forward, some don't.
There are so many holes in this. I feel like whoever wrote this has a strong desire to reduce people to a number. It's not only terrible, it's a great way to fool yourself.