This increasing churn may be one of the key reasons women tend to avoid IT careers. When you feel compelled to do what's best for a family, job and location instability is undesirable.
The California dot-com burst certainly hit me, a father, in the wallet (and family time), as I was job-seeking in a glut market for a few years, taking crappy fly-by-night gigs that remind me of Bob Seger tunes. If I had been a single parent, I'd be screwed.
Whether it's genetics or social norms, women often end up with the primary burden of taking care of family.
[job] Security, has always been and will always will be, an illusion in the work force.
Well, it used to be higher. Something changed. Foreign competition? Internet-based head-hunting giving co's more options? Institutionalized growth and/or worship of greed? Financial data mining favoring churn-and-burn (on paper)?
Perhaps H1B priorities should be awarded based on a company's retraining expenditures to encourage them to retrain rather than dump.
However, it's probably easy to manipulate such numbers, as lot of things can be classified as "training".
Or perhaps on the number of technical workers they have laid off. If a company has a high record of laying off techies of related skills, then their visa worker applications should be rejected.
This is why COBOL and mainframes continue to live on. Applications on them are often 30 or more years old and continue to work.
Companies don't like to pay loads of money for line-of-business apps only to have to pay loads again 12 years later to revamp it for the latest-and-greatest server/language/OS, especially for something with little or no UI.
Microsoft is keeping COBOL and mainframes alive and well.
Based on my experience with political forums, conservatives will flag all progressive viewpoints false and vice versa. Anything controversial will simply have a bunch of flags associated with it. If you only allow "false" flags, then controversy itself would generate tons of "false" flags. If you also allow "true" flags, then you'll get basically an opinion poll, often based on emotion rather than careful research and analysis.
I think it's only recent that electronic cameras have been sensitive enough at a price amateur comet hunters could afford. Plus, it probably takes a lot of hard-drive space to store comparative images.
C is the "new assembler". If you want tighter control over machine resources, then C is the next best thing to assembler/machine-language. CPU's are designed with C in mind even, so it's a 2-way street.
Earlier attempts to unfurl the scrolls yielded some readable material, but were judged too destructive. Researchers decided to wait for newer technology to be invented that could read the scrolls without unrolling them.
Wow, somebody actually planned ahead instead of dived in face first making a mess to get first publishing credit.
In the keyboard: Commodore-64 In a phone: Apple iPhone In the monitor: Apple In a flower-pot: Apple ("daisy monitor") In a flash drive: pendrivelinux.com In a mouse-pad: ? In a power cord: ? In a toaster: http://www.embeddedarm.com/sof... In eye-glasses: Google-glass In undies/bra: ? In a coffee mug: ? In a coffee maker: http://null-byte.wonderhowto.c... In head-phones: ? In a hat? (red hat:-) In green-eggs-and-ham: ?
Google has been wandering too far out from its experience. Space satellites are another head-scratcher project of theirs. The history of big oligopolies wandering off target is not very good. GM used to do that also, and ended up selling off most of their experiments at a loss. And while Xerox did great research outside of copiers (GUI's, Ethernet, etc.), they didn't know how to bring it to market, making bulky, expensive copier-like machines.
I would like to see Google be more aggressive going after the cable co's, however. That's only semi-wandering. The cable model is ripe for the picking: ticked off customers and poor choice. Google has the deep pockets and distribution infrastructure necessary for such a battle.
Ignoring vendor issues and focusing on the language itself, I have to agree. C# is a decent balance between features and readability.
And unlike Python, it introduces students to the "C style" syntax programming, which they are likely to encounter in the work world in the form C, C++, Php, Java, JavaScript, Perl, etc. Python wouldn't give you that. (And Python's "tab issue" will stump a lot of newbies.)
And because it came after Java, it improved on Java for the most part, and thus is superior to Java as a language.
Python is better suited for an advanced course. It's a little "too clever" for a newbie.
Side note: I just wish the C-style languages would invent a better case/switch syntax convention. C's sucks; "break" is dumb. But since it's a training course and students will probably need to know C's goofy case/switch construct in other languages (above), students might as well be shown it. But, do show them better case blocks in other languages and explain C's is an (unfortunate) leftover from a machine-centric era. They are like neckties: an uncomfortable habit from antiquity.
Slashdot Mirror
This increasing churn may be one of the key reasons women tend to avoid IT careers. When you feel compelled to do what's best for a family, job and location instability is undesirable.
The California dot-com burst certainly hit me, a father, in the wallet (and family time), as I was job-seeking in a glut market for a few years, taking crappy fly-by-night gigs that remind me of Bob Seger tunes. If I had been a single parent, I'd be screwed.
Whether it's genetics or social norms, women often end up with the primary burden of taking care of family.
Well, it used to be higher. Something changed. Foreign competition? Internet-based head-hunting giving co's more options? Institutionalized growth and/or worship of greed? Financial data mining favoring churn-and-burn (on paper)?
Perhaps H1B priorities should be awarded based on a company's retraining expenditures to encourage them to retrain rather than dump.
However, it's probably easy to manipulate such numbers, as lot of things can be classified as "training".
Or perhaps on the number of technical workers they have laid off. If a company has a high record of laying off techies of related skills, then their visa worker applications should be rejected.
This is why COBOL and mainframes continue to live on. Applications on them are often 30 or more years old and continue to work.
Companies don't like to pay loads of money for line-of-business apps only to have to pay loads again 12 years later to revamp it for the latest-and-greatest server/language/OS, especially for something with little or no UI.
Microsoft is keeping COBOL and mainframes alive and well.
Based on my experience with political forums, conservatives will flag all progressive viewpoints false and vice versa. Anything controversial will simply have a bunch of flags associated with it. If you only allow "false" flags, then controversy itself would generate tons of "false" flags. If you also allow "true" flags, then you'll get basically an opinion poll, often based on emotion rather than careful research and analysis.
Better yet, dump it, and include an OSS variant in future Windows.
Why doesn't Netflix use Flash, at least as an alternative choice.
We should have forced them to invent (practical) flying cars before those.
I think it's only recent that electronic cameras have been sensitive enough at a price amateur comet hunters could afford. Plus, it probably takes a lot of hard-drive space to store comparative images.
Nukes carry a lot of politics with them even if price was no object.
What about a solar sail that also uses the big planets as a gravity sling-shot?
C is the "new assembler". If you want tighter control over machine resources, then C is the next best thing to assembler/machine-language. CPU's are designed with C in mind even, so it's a 2-way street.
Cool, slashdot 0.001
They called it being "Rick Scrolled" back then.
Wow, somebody actually planned ahead instead of dived in face first making a mess to get first publishing credit.
There is hope for (some of) humanity after all.
You see, the computer is in the mouse, the mouse is in the monitor, and the monitor is in the computer. Gottit?
I prefer the Get Smart factor: shoe-phone. More fun. Gives a new meaning to "reboot".
Jimmy still owes me 10 grand from his prince buddy in Nigeria.
In the keyboard: Commodore-64 :-)
In a phone: Apple iPhone
In the monitor: Apple
In a flower-pot: Apple ("daisy monitor")
In a flash drive: pendrivelinux.com
In a mouse-pad: ?
In a power cord: ?
In a toaster: http://www.embeddedarm.com/sof...
In eye-glasses: Google-glass
In undies/bra: ?
In a coffee mug: ?
In a coffee maker: http://null-byte.wonderhowto.c...
In head-phones: ?
In a hat? (red hat
In green-eggs-and-ham: ?
Do you know that you left yourself wide open* for male anatomy jokes there?
* Not intended to be a "goat_" joke.
Obviously the compiler has a floating point bug.
Are they any good at finding studs...?
Human studs, yes. Building studs, no.
Why is Perl up? It had been going down in use for a while. What event/change/fad sparked an uptick?
Or is it just random ebb and flow?
(I'm not trying to trash Perl, but there is something odd about the trend pattern here.)
Google has been wandering too far out from its experience. Space satellites are another head-scratcher project of theirs. The history of big oligopolies wandering off target is not very good. GM used to do that also, and ended up selling off most of their experiments at a loss. And while Xerox did great research outside of copiers (GUI's, Ethernet, etc.), they didn't know how to bring it to market, making bulky, expensive copier-like machines.
I would like to see Google be more aggressive going after the cable co's, however. That's only semi-wandering. The cable model is ripe for the picking: ticked off customers and poor choice. Google has the deep pockets and distribution infrastructure necessary for such a battle.
Evolution of Passwords:
1978:
password
1983: Rule: Don't use 'password', too common.
passgas
1990: Rule: Must contain at least one digit
passgas7
1995: Rule: Must contain mixed case
Passgas7
1999: Rule: Must contain at least one punctuation character
Passgas7&
2004: Rule: Must change every 2 months
Passgas7& ... Passgas8* ... Passgas9( ... Passgas1! ...
2009: Rule: Don't use same punctuation as digit key
Passgas7$ ... Passgas8$ ... Passgas9$ ...
2012: Rule: Don't use incremental digit patterns
Passgas71$ ... Passgas17$ ... Passgas$71 ... Passgas$17 ...
2015: Rule: Must be at least 20 characters long
Passgas711111111111$ ... Passgas177777777777$ ...
2017: Rule: Can't use any patterns guessable by AI
Oh f$ck it, just hack me already, dammit @666
Ignoring vendor issues and focusing on the language itself, I have to agree. C# is a decent balance between features and readability.
And unlike Python, it introduces students to the "C style" syntax programming, which they are likely to encounter in the work world in the form C, C++, Php, Java, JavaScript, Perl, etc. Python wouldn't give you that. (And Python's "tab issue" will stump a lot of newbies.)
And because it came after Java, it improved on Java for the most part, and thus is superior to Java as a language.
Python is better suited for an advanced course. It's a little "too clever" for a newbie.
Side note: I just wish the C-style languages would invent a better case/switch syntax convention. C's sucks; "break" is dumb. But since it's a training course and students will probably need to know C's goofy case/switch construct in other languages (above), students might as well be shown it. But, do show them better case blocks in other languages and explain C's is an (unfortunate) leftover from a machine-centric era. They are like neckties: an uncomfortable habit from antiquity.