I am curious as to why you would make a statement that "The overseas technical job paranoia is a rumor or hoax!"

PF


>>Igor,
>>
>I think your analysis is one of the best I've seen posted here yet. I believe that VFP's downfall is it's failure to fit in the enterprise structure. This has nothing to do with Microsoft marketing.
>Not all solutions are enterprise solutions. And there is no telling how long .NET will be viable. There are open source tools out there that don't need MS "enterprise" technologies. Everything you need is in the kernel, and almost free (even support).
>
>It is always because of where they want the company to go with their software development.
>It sounds like they're not getting the results they expected from the "team", and less an issue with the development tool.
>
>And they view .Net or Java as a better way to get there. These decisions have been purely technical.
>Thats what they say.
>
>Sometimes projects are less than expected for reasons other than development tool. Projects [can] fail because of a bad plan or lack of depth in the roster. Many times, in these cases, it may be easier to blame the tool. Hopefully - they will get it right the second time around, with a different team, or a differt tool (if that is the problem).
>
>Big corporations (enterprise users) will and have paid millions for solutions they will never use. In these cases, they may just 86 it - or fire the old team and re-do it. If something works - why change it? If something doesn't work - then maybe it's the language or direction issues.. hmmmm.
>
>There are multimillion dollar companies still using quick basic to do their accounting. The only direction they have is accurate, efficient accounting.
>
>However, much like the technical jobs that have gone overseas, never to come back
>The overseas technical job paranoia is a rumor or hoax!
>
>Most of the technical jobs that have gone over seas are call room jobs and data maintenance jobs (for those call rooms). In India, to work in a call room (average job duration 6 months), a BA is required (just to be a phone solicitor or help desk answer guy!!!) The best software, like good rock n roll, is still made in America, by obnoxious Americans.
>
>many of the VFP jobs that have disappeared will never come back.
>Maybe developers that write unappealing VFP apps will never get another VFP job, but ...
>There are a lot of VFP apps in service and I see a lot of VFP jobs on the job boards - but most VFP jobs want people with full system experience, business experience and references to authenticate that experience. Team shops just want people that fit in - skills in many cases, are secondary.
>
>Teams make money by selling man hours. Independents make money through reputation by delivering on schedule and in budget. Two completely different animals.
>
>Because when the hiring begins again, it will be for a different language.
>It might be for different operating systems too! VFP and other xBase tools do well on open source platforms. You don't need .NET on these platforms - you don't need to lease expensive MS licenses on these platforms. You don't need big expensive MS trained coders. Open Source support is one reason companies (and nations) are switching.
>
>It has always been stated here by MS people that VFP will be marketed to the existing VFP market only.
>What do you think that interpretation means. Aside from you, there are about three or four other guys on this board that express that sentiment. You used an infinitive. -10 for lack of objectivity:-)
>
>Gosh I did not know that - I just sold a VFP project to company that fired their non-VFP consultant team. Don't believe every death rumor you hear on this board. The same attitudes that sucked with VFP, now suck with .NET or C# - not to say there are some BAD C#/.NET people working the market:-)
>
>There are features that the enterprise is looking for that will never, ever exist in VFP.
>Like what? ...(again, -10 for using an infinitive)
>
> MS has acknowledged that the enterprise is their main market. VFP has an expiration date of 2010.
>So what?
>
>I have trouble understanding the resistance here on this board. I've known for a long time that I need to expand my skillset.
>Many of those on this board enjoy working with VFP and make a fair living at it. The nay sayers seem not to enjoy their work as much as the advocates.
>
>A solid skill set with any OOP tool will be good. You can dilute your depth, by knowing a little bit of every thing, but neglecting to master any.
>
>I've looked at .Net on my own. Now I am in a situation where they will looking to replace VFP with Java in the next couple years. I work in a team of about 10 VFP programmers.
>I bet MS is happy to hear you're considering Java:-)
>
>Team vs individual mentality. You, my friend, are a team person. Teams swim in schools. Strength in numbers! Full System developers and Independents (with lots-o-happy references) are more like sharks:-). Strength in agression!
>
>The language is secondary to the other skills required to build a project (requirements to sign off). VFP is great for those kinds of projects.
>
>Everyone I work with is on board to learn Java.
>Knowing the VFP OOP paradigm will make learning Java a breeze. It's gonna be hard not having them VFP cursors around. ADO record sets - yukola!
>
>No one is arguing that VFP is great and they don't want to learn anything else.
>You have to learn other things! It's an imperative. But, don't fool yourself into thinking VFP is something less than the the most powerful , fastest development system out there. Java has been around a lot longer than VFP. And all the "brower" solutions I've seen for bean counting apps are slow and zero sex appeal. Browsers solutions are best suited for projects like the UT, internet catalog sales, SQL reports. VFP interfaces, if done right, can present data in all sorts of exciting and fast ways, from all sorts of sources.
>
>That is the nature of our industry.
>Aint it great!
>
>>
>>
>>PF