I'm going to disagree. I haved watched experienced developers learn dotnet in less than 3 months (not a 40 hour week mind you but rather an all day all evening commitment to learning) and become productive developing tools and utilities using dotnet. True, it seems that experienced java and Delphi developers pick it up even faster, but I have seen VFPers do the same. Now, that doesn't mean that they can sit down and develop a full fledged business app from start to finish after 3 months research without a lot of trial and error. But look at it this way, if you look back at your first few apps you wrote, how many would you leave exactly as is if you were developing them today? That does not mean that they don't suffice or don't work correctly, but if you were to write the same app today, I'd venture to guess you would do it alot differently. You would probably startout by creating the portions that could be reused and automatically separate the tiers. You could write most of it without even considering which method is faster, easier to modify or subclass down the road, or easier for other developers to reuse or understand. You would know automatically which method would best suit your purposes. That knowledge comes after years of experience and that is what is lacking in new users of dotnet. It is also true that not everyone has the same aptitude for learning new technologies. Sometimes it doesn't matter how good a developer you are but rather how well you can learn and adjust to new ways of doing things. In those areas, usually the younger the better. I can't believe I just wrote that! :o)

Hi, Tracy,

As always, you've made some interesting points. ;)

In this instance, the three months hasn't been as much about a training period to start working with the product in prime-time...it's become a trial period to determine if the capabilities of the tool are comparable enough to cost-justify developing in it, vesus .NET. It is on this issue where I fundamentally disagree. He gave it the college try for 3 months, and made some conclusions that those with more experience find hasty and not really correct.

It's gotten to the point where, when someone says, ".NET is not ready for me and my needs", what's actually being said is, "I'm not fully ready for .NET". That is not a slam, it's not an attack on anyone, it's simply fact. I know Fox developers who have told me that they don't have the time to learn .NET, it's too much for them to take on. And that's fine - I've never said one unkind word for those who say that. It is when developers turn this around and justify their lack of interest in .NET by getting on the "it's not ready for prime-time" bandwagon where I have an issue.

Many developers are not comfortable using a new tool until they can generally reproduce the same kind of outcome that they can with their current tool (certainly understandable). But that doesn't mean they shouldn't start tackling the learning curve, IF they feel that .NET may become part of their future down the road. It is all about managing one's career.

You're absolutely right...the first stab at an app with a new technology will look different than the 2nd iteration, the 3rd iteration, etc.

This is why it is so important for people to starting looking at .NET now (or 2-3 years ago!), even before it's a big dot on their radar. If one waits until it becomes an necessity to start looking at it, one is already behind the game.

Several have made this point - those who have learned multiple tools over their careers are more likely to ascend the learning curve faster than those who have primarily worked with one tool.

I made some similar comments in Message #1132093.

Kevin