There are some problems you ignored. First is that the industry claims there is a "shortage" to justify high quantities of H1B's. There is no evidence of a general shortage, only spot shortages, which are necessary for those with glut skills to be accepted into new-trend skills.
Second, is that during IT recessions they don't shut off the H1B spigot: visa workers keep coming. IT has been booming and busting since at least the 80's and I see no reason this pattern will change.
And I have seen H1B workers being abused. Your example is only a spot sample.
In general, the industry wants "instant employees" rather than spend time and money on training. This means that if a US techie loses their job in a glut area, they cannot get retraining for the new area because the company will hire an H1B worker that already has experience. The citizen can read books etc., but companies prefer existing paid experience.
Companies just want what they want when they want it and don't want to pay anything inconvenient for these goals.
Regardless of whether there are some H1B abuse myths floating around, the whole premise is based on a lie.
Georgia? The locals will do it for free if you spread the rumor that "Obama's commie drones are coming to take your guns away and spray you with 'gay gas'."
Until you get really sick or run off to Argentina with Miffy, and then the remaining staff hasn't a clue about how to run or fix all the custom contraptions.
Let's have some perspective here: this is the first time a website of this magnitude and complexity has been created on the federal level, at least any that had to be completed within a relatively short time-frame.
Learning programming is relatively easy. Learning to write maintainable code, on the other hand, takes skill and experience.
Clerks and accountants used to do amazing things with Lotus-1-2-3 macros because Lotus cleverly leveraged what users already knew about spreadsheets into a Turing Complete set of commands. But often these users eventually got themselves into a jam, or made something that nobody else could decipher.
The funnest job in the world would be to create fake front sites for dictatorial countries. For example, I'd make "CNN.com" grab content from onion.com, and stupid.com content would be used to fill up "Amazon.com".
In "1984", the main character's job was to re-write history with fake BS. He seemed fairly content at that job until he took the proverbial red pill.
That often doesn't fly. You have to choose your battles carefully, and not be seen as "complaining" about everything. Before being "forceful" over an idea that was originally rejected, make sure it's something that really matters and makes a difference.
Slashdot Mirror
A terrorist walks into the White House bar. The bartender asks, "So what will you be having?"
"72 virgins"
"Sorry, we don't serve that here. How about a Bloody Marry instead? Almost the same."
They should have a fake breakin attempt every 3 months or so to keep everyone alert. Complacency can settle in if nothing ever happens.
Maybe there is a reason it's not locked.
There are some problems you ignored. First is that the industry claims there is a "shortage" to justify high quantities of H1B's. There is no evidence of a general shortage, only spot shortages, which are necessary for those with glut skills to be accepted into new-trend skills.
Second, is that during IT recessions they don't shut off the H1B spigot: visa workers keep coming. IT has been booming and busting since at least the 80's and I see no reason this pattern will change.
And I have seen H1B workers being abused. Your example is only a spot sample.
In general, the industry wants "instant employees" rather than spend time and money on training. This means that if a US techie loses their job in a glut area, they cannot get retraining for the new area because the company will hire an H1B worker that already has experience. The citizen can read books etc., but companies prefer existing paid experience.
Companies just want what they want when they want it and don't want to pay anything inconvenient for these goals.
Regardless of whether there are some H1B abuse myths floating around, the whole premise is based on a lie.
Erect a giant Jar Jar, then the fanboys will be all pissed and lose interest in snooping. Solved!
Georgia? The locals will do it for free if you spread the rumor that "Obama's commie drones are coming to take your guns away and spray you with 'gay gas'."
But it's so cool how your hip glimmers at night.
Until you get really sick or run off to Argentina with Miffy, and then the remaining staff hasn't a clue about how to run or fix all the custom contraptions.
It's the same reasoning that makes us all think that slashdot ridding dupe articles should be easy.
F-35 did at least one thing right: didn't depend on a big website.
Let's have some perspective here: this is the first time a website of this magnitude and complexity has been created on the federal level, at least any that had to be completed within a relatively short time-frame.
...get out the big-grained salt shaker.
5 Billion? Hell no. A Washington Post article on the website costs:
http://www.washingtonpost.com/...
Not according to iMaps
Go into the bankruptcy paper-work business. If you ever have to file bankruptcy, you'll be ready.
2075: "A tab? How quaint"
BSOD DNA=TMNJ
Wakes up, "WTF? I have a....Vagina!? Hoooneeeyyy!"
Learning programming is relatively easy. Learning to write maintainable code, on the other hand, takes skill and experience.
Clerks and accountants used to do amazing things with Lotus-1-2-3 macros because Lotus cleverly leveraged what users already knew about spreadsheets into a Turing Complete set of commands. But often these users eventually got themselves into a jam, or made something that nobody else could decipher.
The funnest job in the world would be to create fake front sites for dictatorial countries. For example, I'd make "CNN.com" grab content from onion.com, and stupid.com content would be used to fill up "Amazon.com".
In "1984", the main character's job was to re-write history with fake BS. He seemed fairly content at that job until he took the proverbial red pill.
"Get off my red lawn!"
That often doesn't fly. You have to choose your battles carefully, and not be seen as "complaining" about everything. Before being "forceful" over an idea that was originally rejected, make sure it's something that really matters and makes a difference.
What's wrong with complacency? You get really used to it after a while even.
Amazon discovered it was for sale when they visited "buy.buy".