Ultimately, that line of thought ends with me developing my own algorithmic feed, which I don't really want to do and isn't scalable anyway.
1,797 karma · joined January 20, 2011
Ultimately, that line of thought ends with me developing my own algorithmic feed, which I don't really want to do and isn't scalable anyway.
I need an algorithm for that. There's no good way for me to say, "I don't want to see all the stupid shit she posts, but please show me important stuff" because I lack the ability to rigorously define "important stuff". And it's unreasonable to treat her unwillingness to personally text those updates to every single person she knows.
To the extent that it's relevant here, that appears to be untrue. This hinges on the fact that with an API, you have to match it exactly, and there's no reasonable way to argue that someone could sit down and do a clean room implementation of the Java APIs that perfectly matched all 3000 classes and all the public interfaces of all those classes.
You can do a clean room implementation of the Java Platform, but you can't do a clean room design of the Java APIs. The whole point you're trying to solve is to make something that's compatible with Java, and that requires knowing the Java APIs, i.e., it's not a clean room. If we extrapolate that back to IBM and clones, as long as the clone makers must come up with the same external API as the IBM BIOS, then this court would say that IBM absolutely could use copyright law to prohibit clones, because the clones would have to have copied the APIs -- not the code, but the names and types used in the APIs themselves, and IBM holds copyright to those names.
What do you put down for a drug overdose? Was he chasing the next good time or escaping the pain of being molested as a child?
It's basically this. Imagine I have two data sets that are identical, except one has your specific data and the other doesn't. It's possible in some circumstances to infer information about you by asking for things like averages on the datasets. Differential privacy is a method for defeating attacks that rely on that type of "leakage" of information. It assures that if two datasets are close enough, queries on those datasets will not yield significant information about their differences (i.e., the presence or absence of one particular data point won't be detectable).
It's all about how queries of the data perform, and not at all about the data itself.
But yeah, certainly the more populated areas are extremely English-friendly. My folks in Arkansas probably see more non-English speakers in the average month than I did in Reykjavik.
So we can say that's a bad spec if we like, but what's the answer that leads to? I don't need an AI if I can just declare all users must be really good programmers spending their days writing unambiguous specs. That wasn't really the goal of the AI though.
Reinforcement learning turns out to be fantastically clever at finding really stupid solutions if you give it the tiniest opening to do so. You put a camera in a room to provide feedback for an agent to learn to move an object closer to the camera, and it will happily learn to knock the camera over.
Since you missed it, the point was this: it's irrelevant that he posted it on a company board that was asking for opinions, so stop trying to use that as a defense. If you want to defend what he said, go nuts. We can argue the merits and whether Google overreacted. Just don't whine, "but they asked his opinions!" as though that's some sort of shield.
If my boss says, "Hey deong, what do you think about black people?", that's not a get-out-of-jail-free card for me to start dropping n-bombs. There's one answer you're allowed to give to that question, and it's not because there's some conspiracy to oppress dissenting opinions. It's because there are extremely reasonable standards for employment that include not shouting racial epithets and white supremacist propaganda. Being asked your opinion doesn't change the rules.
Damore was certainly less inflammatory than that, but the point remains. You can argue that his opinions didn't warrant firing, but there's no reasonable way to argue that because he was responding to requests for comment, it's unethical or otherwise shady to hold him accountable for those comments.
* MS-DOS/Windows 3.1-like * Windows 95-like * Windows 8-like
Windows 8 basically was born and died in a couple of years, to be replaced with Windows 10, which is very much the same basic set of metaphors as Windows 95. There's a start menu, a little dock of pinned icons next to it, a taskbar, a clock and some little icons for what are basically background processes. There's a maximize and minimize and close button on windows. There's a File/Edit/Whatever set of menus. You can right click for context items, many of which are consistent with Windows 95 20+ years ago. That basic system is now something like 21 years old now.
You can maybe argue that Microsoft forgot your message five or so years ago, but they obviously rediscovered it.
Anyone wanting to live in Nashville (just to pick one city from the list) who's capable of working for Amazon is also capable of working for someone in Nashville today. And generally, the economics of being tech talent outside these hotbed markets like SV and Seattle are vastly favorable.
That is to say, you're probably better off buying the cheap house in a smaller market on the salary you can command in that market than you are buying a very expensive house on the salary that the very expensive market offers you. Google would pay me more than my current job, but my cost of living would go up by more than my salary -- massively so.
Google does explicitly ask you for permission to do this. And whenever someone in this thread points that out, someone replies with some variation of "yeah, but they probably do it anyway". Well...OK then I guess. There's not much of a conversation that can happen after that, but you do you.
I would argue that the level of knowledge, talent, and engineering and scientific resources required to do what Google does forms a pretty effective natural barrier to a bunch of small players being able to compete.
Except for the many thousands that have been known, from every exploitable vulnerability that's allowed an iOS jailbreak to every security fix in every patch in the nearly two decades of OS X (and System 7/9/etc before that). These types of things are fairly complex pieces of software. It doesn't matter if the software is ultimately compiled to hardware circuitry or executed by a CPU -- bugs come from complexity, not from the medium.