10 years of experience does not equate to a great violinist, but I don't know any great violin players without it.
I started writing code at a young age, got a CS degree, and after graduating my first 3 months I was more productive than some people I have worked with with 5 years experience. I created something that a significant fraction of people I have worked with would have been unable to think of. However, I had just been writing code not reading it. After working on many projects both short and long term, I would cringe if I had to maintain the code I wrote back then.
Comments are a probably the perfect example where you need to be bitten by a stale comment a few times to really understand what's important.
You don't need 10 years, you need 10,000 hours. However, 10,000 hours alone is still a useless metric unless you know it was spent learning. 10,000 hours fixing bugs in the same system won't introduce you to enough new concepts to provide the same value of 10,000 hours of building products.
I started writing code at a young age, got a CS degree, and after graduating my first 3 months I was more productive than some people I have worked with with 5 years experience. I created something that a significant fraction of people I have worked with would have been unable to think of. However, I had just been writing code not reading it. After working on many projects both short and long term, I would cringe if I had to maintain the code I wrote back then.
Comments are a probably the perfect example where you need to be bitten by a stale comment a few times to really understand what's important.