Actually, as a "nearshore" vendor, I can honestly tell you that your problem isn't just offshoring, per-se.
Your problem is a combination of rampant and irresponsible "offshoring sales" (i.e. companies selling services they're not really up to part to deliver based solely on price which, btw, borders on dumping), ignorant management who just eats up the "price" argument thinking they can get a mercedes benz for the price of a yugo, and their disillusionment after being conned for years by incompetent IT workers charging astronomic salaries while at the same time not being worth those salaries.
Think of it: how many times have you been in a position where you are mad that you're having to clean up some incompetent slob's IT messes and wonder why they weren't let go rapidly? If your answer is "not too often at all", then I envy you. Sadly, the truth is often the opposite case.
The combination of these morons charging an arm and a leg (comparatively speaking), and management that is less than informed is fatal: even less-than-smart managers will come to the realization that it's better to get sucky labor for cheap than do it expensively. Even worse: true-blue-idiot managers think they can actually do BETTER.
Granted - sometimes they will, but this is by far the exception, not the rule, and is such a crapshoot it ain't even funny.
Bottom line: you want to keep and protect your job? Stop worrying about keeping and protecting it, and start worrying about how you can bring more value, produce more, be more efficient, etc. In the end, if you get canned for it, then you were already on the chopping block anyway and just didn't know it.
If not, then you're much more likely to be considered a valuable resource and your cost to the organization will be more than justified.
Bottom line: when an employee's value matches or outweighs their cost to the organization, the employee is a keeper regardless. Most managers - even stupid ones - think in those terms.
Brew fresh coffee. Take care of the food orders (and maybe go for special pick-up as a treat). Make sure anything that hinders their smooth progress is handled by you. Noise? Go deal with it. Something not where it should be and makes their life harder? Chase it like a rabbid dog and solve it. The best way to ensure their success (and thus cover your ass, if that's your persuasion) is to, precisely, do whatever you can to remove the obstacles to that success.
But heed the warning: if you're staying just so you can keep an eye on them, you're making a huge mistake. If you don't trust them in overtime, then you have no reason to trust them in normal work hours, and your problem is something much bigger and uglier.
Simply put - though VB was "wildly successful" - but how many pieces of software built on it are still around *because they were built properly*? Most of those tools have been thrown aside because they were grossly inadequate in performance, architecture, design, etc.
I was a witness to countless fusterclucks and saw how many systems had to be re-done from scratch because some genius businessman believed what he read on the brochures only to realize that there was no such promise and now his hordes of customers were demanding delivery on the promises made. Needless to say, there were no shortage of *REAL* programmer jobs in those days
The problem was never with the language per-se, as I'm sure the problem won't be with Rev4. The problem was always with design, architecture, concepts, and implementation choices. As noted above by the xkcd reference, there's no substitute for clarity regardless of the tool you choose to implement your program.
I'm not knocking the tools themselves, I'm knocking the fact that they're billed as ways to "bring programming to the masses".
Just like not everyone should handle nuclear material or toxic substances or operate on a human body, not everyone should *program* computers. As such, the really big benefit I see for this kind of tool is as an end-user interface mechanism (or facilitator) - especially in conjunction with language recognition. There are some interesting ideas there that are definitely worth exploring...
The intelligence of any discussion diminishes with the square of the number of participants. -- Adam Walinsky