2,169 karma · joined May 25, 2009
AI is massively popular in both industry and academia at the moment. It is at no risk of being deinflated by "anti-hype".
Why do you single this out as an especially male phenomenon?
There's a massive bias in our historical records towards Europe. But Europe has also seen a lot of wars.
No, that's inaccurate.
For instance, one example the article used to support WiB was that x86 (a CISC architecture) beat out RISC architectures. There were many RISC architectures: MIPS, SPARC, DEC Alpha, PA-RISC. So it's not a case of worse is better than nothing. x86 won against real competition, because it took advantage of evolutionary pressures.
Worse-but-Better solutions make it to market dominance before the Right Thing has a chance to get off the ground; and then the Right Thing is no longer the right thing, because the reality has changed.
Taken uncharitably, of course, it sounds like puffed-up nonsense, which perhaps it is.
This is not true. Ownership is only relevant in the presence of mutability. In a GC'ed language where most or all data is immutable, one rarely needs to think about ownership. In Rust, one needs to think about it all the time.
Rust is certainly a leg up compared to trying to write multithreaded C or C++ code, but that doesn't mean its approach is free of drawbacks.
Empirically, even in Python - a mutable-by-default language - I find myself rarely having to think about ownership. That could be an artifact of the kind of Python programs I find myself writing, though. I'd be interested to hear other people's experiences on that front.
The article brings up many more flaws with the external review than the use of that anecdote. For example, the misreporting of statistics (70% vs 30% of patients meeting the criteria for gender dysphoria); the low number of interviews with actual patients of the GIC (9 or 11), of whom even so only 2 had complaints; misreporting the nature of the use of play therapy (for assessment vs treatment); and so forth.
If the GIC is to be condemned (as perhaps it should) for conversion therapy, it should at least be done on the basis of a thorough, fact-checked independent review; the article's thesis is that the external review conducted by Zinck and Pignatiello does not suffice. It's not just one anecdote they take issue with.
> His approach involved telling parents to prevent their kids from playing with toys of the "wrong" gender [...] > His position - what he told parents coming to his clinic for help [...] > I've followed this issue, [...]
Do you have any links you think are particularly informative about the practices of the GIC in this regard?
That's sexual orientation, not gender identity, no? One of the salient points in the original article is precisely the distinction between gender identity (which the GIC sees as flexible, but their critics see as immutable) and sexual orientation (which both appear to view as immutable):
> GIC clinicians view this as a conceptual error: The critics are conflating sexual orientation — which can’t be changed, which is part of the reason we view attempts to mess with it it as unethical — and gender identity, which they say isn’t some hardwired thing
But if we're interested in whether the industry itself has a problem, in whether a problem exists, then we should take women (or anyone else!) at their word when they say they experience harassment, absent strong evidence that they are lying or mistaken. Otherwise, we are violating the same rule: assuming they are guilty of lying until they prove themselves innocent!
My default assumption is that when there are claims of harassment, there is some substance to them, even if the specifics are wrong. Bringing forward claims of harassment in the tech world turns your life (and that of the accused, if their name is publicized) into a shitstorm; people don't tend to do that without reason. But this is just a heuristic. It looks like Horvath's claims of harassment might be unsubstantiated in this case.
It's hard to tell, though, because most of the things she complains about (with the exception of the code-review stuff, which appears to be just false, which is worrying) is unverifiable outside of he-said/she-said. Note the noncommittal wording: "The investigation found no information to support misconduct or opportunistic behavior by the engineer against Julie or any other female employees in the workplace." No information to support suggests "neither evidence for or against". Which is natural. Harassment is hard to prove or disprove precisely because it usually doesn't leave evidence.
> there was an apparently thorough investigation by a reputed external investigator who found that the claims were false. [...] And yet this single person's claim was enough to force out the CEO
Specifically regarding the ousting of the CEO, let me quote the investigation you linked:
> The investigation found Tom Preston-Werner in his capacity as GitHub’s CEO acted inappropriately, including confrontational conduct, disregard of workplace complaints, insensitivity to the impact of his spouse's presence in the workplace, and failure to enforce an agreement that his spouse should not work in the office.
Harassment does say something about the culture in which it happens. What you're pointing out, correctly, is that it's not exceptional for this kind of stuff to happen - that Github is probably not much worse than most other tech companies in this respect.
As you say, this is no excuse. Change has to start somewhere; we can't keep saying "oh, it just happens, you know, it's not worse here than anywhere else".
> Maybe Github should split into a corporate division and an open source division. The OSS division could make all of its work and decision making distributed and public, and the corporate division could do business development and attack new market opportunities.
I would like that, but how would it make investors money? If the answer is "it doesn't", then it won't happen.
Of course, if the compiler is incorrect it might generate incorrect code, but then the "proof" that the code is correct would not check.
Mind you, it's very ambiguous to describe what their compiler is doing as producing a proof of "correctness". Any time someone says "correct", you should ask, "correct with respect to what?" In this case, AIUI, their compiler produces: (a) a formal description of what the program does (what they call "a high-level shallow embedding of the program's semantics") (b) a proof that this is in fact what the program does (its "correctness")
The idea being that if you want to show that your program is actually correct with respect to the specification you really care about, you do the proof on the formal description (a), and then (b) automatically guarantees your proof carries over to the actual program.
[1]: https://plus.google.com/110981030061712822816/posts/KaSKeg4v...
They're both vaguely accurate but break down if you try to credit them with too much explanatory power (as Yegge does, IMO, but Oakes doesn't seem quite as reductionist).
To my mind, the fields which are known for requiring training from childhood are sports and the performing arts (music, theatre).
And if I had to guess, I'd speculate this is less because it's intensely difficult to play sports or learn to play music, but because so few people can become professionally successful in these fields (there's only room for so many sports/music/film stars). CS doesn't have this problem (the demand for programmers is skyrocketing), so we shouldn't expect folks who learned to program in childhood to have any more than a mild-to-modest advantage.
I've heard that idea in a lot of places, but it's never matched up with my personal experiences. I did my undergraduate at CMU, and plenty of the better programmers there I knew hadn't done any programming before they came to CMU.
But of course, this too is anecdata.
> People tend to discuss Silicon Valley’s diversity problem in binary terms. One camp says companies are biased against underrepresented minorities, or at least aren’t trying hard enough to attract them. The other says there aren’t enough people from these backgrounds who are qualified for positions—or at least who are good enough to beat those Stanford grads with all the programming trophies and internship experience and Mozart-like childhoods. The reality is, both are true.