>>>>>> But arguing for NEW vfp dev to typical investors / management can be harder than the task set for Sisyphos
>>>>>
>>>>>Where did you read that from? Your imagination?
>>>>>
>>>>>This statement is an obvious truism to anyone…
>>>>
>>>>A few years ago I was at a job interview with one of the biggest IT companies here in Norway, with more than 10 000 employees, mostly programmers. The interviewer kindly suggested that I refrained from even mentioning VFP, both to them and in any other later job seeking activities.
>>>
>>>I = Interviewer
>>>T = Tore
>>>
>>>I: So what have you done during the past 60 years of your profession?
>>>T: I used to build a lot of successful projects in VFP, and...
>>>I: Please don't mention the V-word here, this is commonly frowned upon!
>>>T: But VFP was a great…
>>>I: Shhh… someone might hear you.
>>>T: I only wanted to…
>>>I: Silence!!!!
>>>T: But...
>>>I: Get out! Next!
>>
>>Actually, they understood that VFP gave me a lot of OOP experience, but that was all the value they saw in it. I have had the same experience in other discussions. After Aruba, I even finished a six month VFP project. successfully, only to be told that they had decided to not use my solution after all. Guess why? Outdated technology...
>>
>>Need I tell that the one who made that decision, was a self proclaimed Guru? I later proved to my earlier boss that this guy knew absolutely nothing about programming. He was a "system administrator", clearly knowledgeable in that field. But would you ask Lewis Hamilton for advice if you wanted to buy a new family car?
>
>Tell me about it. Well if you don't know much of anything you've got to become an administrator. Whoever came up with that profession?
Those who can't do the work, teach. Those that can't teach, administrate. Those that can't administrate, run for political office. :)
Greg Reichert