When you survey them, LinkedIn's professional managers say they want "soft skills". When you check their job requirements, they want you to be have "hard skills" (including N years of experience in their specific environment). When you check who is actually working for them, you find people who are cheap and have little in the way of skills (soft or hard) beyond checking StackExchange.
Yeah, it means "indirect". It's like "literal" meaning "figurative". At this rate, words will have no meaning at all sometime between January 2025 and September 2031.
Insulation in Hawaii is generally crap. And forget true basements; what Hawaiians calls a basement is just the lower level of a house built on a slope.
For professional programmers, the most important skill is sniffing out unnecessary work (requirements that will be changed) and putting it off.
But if we're talking scientists using code in their work....
1) Learn to name your variables. No, nobody knows what "d2" is, and knowing it's "delta sub 2" doesn't help much either. Yes, I know your papers are filled with random symbols that are never explained and no one will call you on because they don't want to look stupid, but that's not proper practice in programming, unless you're a Real Programmer. And you're not; the last Real Programmer died at his terminal in early 1999, when he figured out he was going to get the blame for all the Y2K bugs.
2) Subroutines, methods, functions. Yes, you too can use these. Cutting and pasting code and changing variable names instead... not a good idea.
3) Tests. Yeah, you're going to need them. Or you're going to have to retract that paper because your code had a bug and your results were an artifact.
4) Beware loss of precision. Scientific programmers have spent a lot of time thinking about this. You will too.
5) Source code control. Learn to use it.
With some rather generous assumptions -- a 42,000 BTU, 5.3KW unit costing $10,000 (installed) in each classroom, 180 days of school per year with the unit operating at full power for 10 hours a day -- I get break even in 9 years assuming no additional expenses. This isn't terrible but I suspect with more realistic assumptions break even would take much longer.
Can this bot win edit wars, get Wikipedia administrators to side with it, drive n00bs off its pages? Without that, it's not very useful on Wikipedia itself.
Want the job? Show up late with an electric guitar and amp, do a line of white powder (dextrose, cocaine, your choice) before introducing yourself, and first thing you do is ask whether you're at the right company -- but get it wrong.
If/. adopted the BSD code of conduct, your comment would be in violation at a minimum of "Unwelcome comments regarding a person's lifestyle choices and practices".
You forget the cardinal rule of such CoCs: "It's OK when we do it to you".
voice recognition systems which can't handle various accents
Has not a damned thing in the world to do with the diversity of the team (which, I assure you, in any of the major companies doing speech recognition contains people with all sorts of accents). Has to do with it being a hard problem.
The accuracy of COMPASS is what it is. That it can be matched by untrained humans, or by a simpler calculation, does not make it any less accurate. If age and number of priors between them cover all the predictive factors among the 137 variables, no algorithm can do better than using just them.
They want to make sure the _right_ people get in. Just like in the past. Only now the _right_ people are junior activists rather than the scions of socialites.
Dhillon recently won an abuse-of-process case against a Berkeley Antifa leader.
Sorry about the Breitbart link, but while some of the mainstream media reported the suit when it was filed, I didn't find a mainstream source for the _outcome_ in a quick search. Odd, that.
Political views are not protected classes under employment law.
Turns out they are in California.
He can certainly argue that it had to do with him being white or male, but that's going to be a steep hill to climb given a lot of the diversity reports issued by companies like Google show they're dominated primarily by white men.
Whites are under-represented at Google. The press considers Asians white in SV; the law does not make the same judgement. Besides, employment discrimination does not require disparate impact; disparate treatment is sufficient.
"Race" is a protected class; at least according to the statute, it is as illegal to discriminate against blacks as whites. "Sex" is a protected class; at least according to the statute it is as illegal to discriminate against men as women. Age is also a protected class, but only for people over 40 (yeah, it's a strange law); it's illegal to discriminate by age over 40.
I don't know about Adagio&Fugue, but I'd bet anything containing the first note, or certainly the first three bars, of Bach's Toccata and Fugue in D-Minor garners many infringement notices.
Slashdot Mirror
So they should ban Communism? That'll be the day; every other Google Doodle is celebrating a communist.
The 74% is counting all whites; the 61% non-Hispanic whites.
When you survey them, LinkedIn's professional managers say they want "soft skills". When you check their job requirements, they want you to be have "hard skills" (including N years of experience in their specific environment). When you check who is actually working for them, you find people who are cheap and have little in the way of skills (soft or hard) beyond checking StackExchange.
Yeah, it means "indirect". It's like "literal" meaning "figurative". At this rate, words will have no meaning at all sometime between January 2025 and September 2031.
Insulation in Hawaii is generally crap. And forget true basements; what Hawaiians calls a basement is just the lower level of a house built on a slope.
For professional programmers, the most important skill is sniffing out unnecessary work (requirements that will be changed) and putting it off. But if we're talking scientists using code in their work.... 1) Learn to name your variables. No, nobody knows what "d2" is, and knowing it's "delta sub 2" doesn't help much either. Yes, I know your papers are filled with random symbols that are never explained and no one will call you on because they don't want to look stupid, but that's not proper practice in programming, unless you're a Real Programmer. And you're not; the last Real Programmer died at his terminal in early 1999, when he figured out he was going to get the blame for all the Y2K bugs. 2) Subroutines, methods, functions. Yes, you too can use these. Cutting and pasting code and changing variable names instead... not a good idea. 3) Tests. Yeah, you're going to need them. Or you're going to have to retract that paper because your code had a bug and your results were an artifact. 4) Beware loss of precision. Scientific programmers have spent a lot of time thinking about this. You will too. 5) Source code control. Learn to use it.
With some rather generous assumptions -- a 42,000 BTU, 5.3KW unit costing $10,000 (installed) in each classroom, 180 days of school per year with the unit operating at full power for 10 hours a day -- I get break even in 9 years assuming no additional expenses. This isn't terrible but I suspect with more realistic assumptions break even would take much longer.
Can this bot win edit wars, get Wikipedia administrators to side with it, drive n00bs off its pages? Without that, it's not very useful on Wikipedia itself.
Want the job? Show up late with an electric guitar and amp, do a line of white powder (dextrose, cocaine, your choice) before introducing yourself, and first thing you do is ask whether you're at the right company -- but get it wrong.
So clearly Microsoft should team with Lopez and Marx and call it "Avenue Q".
You forget the cardinal rule of such CoCs: "It's OK when we do it to you".
Has not a damned thing in the world to do with the diversity of the team (which, I assure you, in any of the major companies doing speech recognition contains people with all sorts of accents). Has to do with it being a hard problem.
Prior art is to be found in "Thiotimoline to the Stars".
The accuracy of COMPASS is what it is. That it can be matched by untrained humans, or by a simpler calculation, does not make it any less accurate. If age and number of priors between them cover all the predictive factors among the 137 variables, no algorithm can do better than using just them.
Enhanced wireless 911, including location information, was done years ago.
They want to make sure the _right_ people get in. Just like in the past. Only now the _right_ people are junior activists rather than the scions of socialites.
Maybe that's where you got it. I got it from an episode of JAG.
Dhillon recently won an abuse-of-process case against a Berkeley Antifa leader. Sorry about the Breitbart link, but while some of the mainstream media reported the suit when it was filed, I didn't find a mainstream source for the _outcome_ in a quick search. Odd, that.
Turns out they are in California.
"Race" is a protected class; at least according to the statute, it is as illegal to discriminate against blacks as whites. "Sex" is a protected class; at least according to the statute it is as illegal to discriminate against men as women. Age is also a protected class, but only for people over 40 (yeah, it's a strange law); it's illegal to discriminate by age over 40.
I don't know about Adagio&Fugue, but I'd bet anything containing the first note, or certainly the first three bars, of Bach's Toccata and Fugue in D-Minor garners many infringement notices.
I can think of no possible way this could be abused as political censorship to, say, protect the incumbent government from inconvenient reporting.
2^77,232,917 + 1
The paper appears to claim that Spectre can read memory from a different process, provided it can get that process to do things by giving input to it.
It's the plantation in Gone With The Wind. Don't be surprised when it burns down.