Hi Mark

>What does it mean to 'master' a language?

This is a good question.

>'Mastering' a language is very subjective. There is no benchmark for 'mastering' a language ... and yes, I do believe that certifications can be very misleading and at best are considered a very 'rough' gauge. Since technology changes at a very rapid pace, certifications are merely a gauge of obsolete studies.

I can only speak for myself: As an acid test, I feel I have mastered a language when I become bored with it - this happens when there is nothing more I can learn about it which can be quickly applied to real-world solutions. This also is a function of the technologies of the language itself (e.g. the jump from FPW2.6 to VFP)

I dove into VFP a little over two years ago. I quit my job last year to give myself nine months of intense learning and to build a VFP framework (yet to be completed) in the process. I'm glad I did it because I am applying what I have learned to my current gig. It seems as if the more I know, the more I need to learn. I'm far from being bored.

VFP has been criticized for it's steep learning curve. This is the double-edged sword which is partly the reason for it's lack of wide acceptance and use.

Being philosophical: Important things which are difficult to achieve and/or maintain (e.g. marriage, career, etc.) require a level of committment. Sometimes, we pick losers (e.g. wives, husbands, careers). In the long-run, VFP may turn out to be a loser. Until then or I get bored (which ever comes first), I can do no more than dabble in another language.

I know there are those who disagree and I respect that. This subject is controversial and personal in nature, but it should be talked about.

>Walter, I agree with your thoughts regarding new projects. I would contract someone who feels comfortable with a given language and learn from their work.

Absolutely.