Alexandru Popescu wrote:
In my code/music metaphor I was thinking more of what I find interesting
to listen to; less and less makes a big impression on me (though this
could just be a sign that I'm turning into my parents).
I suspect that with various programming languages, as you internalize
the idioms, you're less struck by how clever something is; you may
think, "That's just how it's done."
So, what you are trying to say is that by the time you may become
blase.
No; that's too cynical. I'm saying that naivety distorts appreciation.
I expect that 99% of the people on this list have gone back to look at code they wrote some time ago, code they were quite proud of at the time, and cringed. Or created what they think is some neat hack, rushed of to show their more experienced co-workers, only to learn that they've finally discovered a common idiom of the language. Acquiring a more critical judgment is not being blase.
If so, than where is the passion? Has all burnt down?
"I don't care for it" is not the same as "I don't care."
There's a difference between judging something to be crap, and believing that it must be that way by necessity.
Going
back to code/music metaphor, this would translate that most of the
composers would just stop composing because they have enough. And I
really cannot agree with this.
Well, that's a misreading of what I wrote. Composers may be more driven as they learn more, because the challenge gets harder, while expereinced listeners have a diminissed tolerance for crap, because over time poor music doesn't bear up. So they demand better.
There's less novelty for you to misinterpret as mastery.
It looks like we are having a different perspective/interpretation of
mastery. And probably, we should agree to disagree. For me a
masterpiece will still be a masterpiece, whatever my understanding
level will be.
But the ability to recognize a masterpiece should change with your level of understanding, and that's my point. People looking for masterful code need some frame of reference both to spot it and to appreciate it.
Asking for examples of masterful code is only half the journey.
Growing up, people told me about masterful composers, and I listened to their works, but it was only years later, after exposure to a lot of music, that I could really appreciate what made a work great (or not).
···
On 6/4/06, James Britt <james_b@neurogami.com> wrote:
--
James Britt
"The greatest obstacle to discovery is not ignorance, but the illusion of knowledge."
- D. Boorstin