This reminds me of one of the SIGs here... "If you think it is expensive to do it right, then wait until you find out how expensive it is to do it wrong", or something like that. I keep telling my general contractor, "Don't send the plumber to work on the framing." I think of the similarities between housing construction and programming. Similar for the jobs - jacks of all trades types at lower pay and craftsmen at higher pay. Assigning a task to an individual with the wrong skillset is very expensive. Just because the cost to WRITE the software is initially less expensive does not necessarily mean you are saving money over the term of the project, it only apepars that way. The bug fixing, constant QA, other miscellanous efforts and expenses, lost customer goodwill, delayed releases, etc. can more than outweight the initial savings you see on the ledgers for the initial development cost. And then, god forbid, you end up with a grossly infgerior design and implementation - you can almost never get that maintained correctly. This goes for programming regardless of location, nationality, etc. I've seen better runs in my shorts! - Patches O'Houlihan