Showing posts with label Shanley Kane. Show all posts
Showing posts with label Shanley Kane. Show all posts

Friday, February 19, 2016

STEM And Competence Vs. Credentialism

Scott Alexander wrote and then disappeared a great, long, rambling rant about various matters, in part related to credentials vs. competence. This sparked a spirited conversation in the comments, which is all we have of it now. (I suspect he plans eventually on trimming it down to fighting weight, and republishing it then.) I wanted to focus here on this snippet (quoted parts are from Alexander's original):
The Blue Tribe protects its own and wants to impoverish anyone who doesn’t kowtow to their institutions. For the same reason, we get bizarre occupational licensing restrictions like needing two years of training to braid people’s hair, which have been proven time and time again not to work or improve quality.
The opposite of credentialism is meritocracy—the belief that the best person should get the job whether or not they’ve given $200,000 to Yale. In my crazy conspiracy theory, social justice is the attack arm of the educated/urban/sophisticated/academic Blue Tribe, which works by constantly insisting all competing tribes are racist and sexist and therefore need to be dismantled/taken over/put under Blue Tribe supervision for their own good. So we get told that meritocracy is racist and sexist. Colleges have pronounced talking about meritocracy to be a microaggression, and the media has declared that supporting meritocracy is inherently racist. Likewise, we are all told that standardized tests and especially IQ are racist and hurt minorities, even though in reality this testing helps advance minorities better than the current system.
As we saw when Asians rose up to block Democratic efforts to reinstate affirmative action at the University of California,  the winners and losers in such efforts are not always readily discernible. But when that same UC pronounces meritocracy as microaggression, you know which direction the system's overlords intend to take the discussion: toward more credentials, and less actual aptitude. Popehat collective blogger @ClarkHat* suggested why progressives have a love/hate relationship with STEM disciplines:
I seem to recall Alexander mentioning a "Silicon Valley 2.0" as a place taken over by credentialists, which would be a field day for people like the censorious Anita Sarkeesian (who lately seems to have snuck into Twitter's censorship board) and naked lunatics like Shanley Kane, whose editorial stance is that competence is the new sexism. I would hope it goes without saying that these people must be resisted with every tool at our disposal.



* I've since been informed that ClarkHat no longer writes for Popehat.

Sunday, August 16, 2015

Shanley Kane, The Backstory

My fascination with Shanley Kane as a manifestation of feminist psychosis got a doubling or tripling down today in the wake of a tweet from Milo Yiannopoulos, who resurrected three old columns of his. There's a lot of linked material therein, but I wanted to hit the highlights.
  • In which Andrew Auernheimer makes the mistake of sleeping with the former racist, which probably amounts to birds of a feather. Auernheimer, in case you forgot, is "a convicted hacker, a prolific internet troll, a self-confessed anti-semite and, as we reported in October, a white nationalist—though he prefers the term 'pan-European supremacist.'" So he has his reasons to misrepresent Kane's positions, now or then. But her untethered loathing for men — "She does, however, legitimately hate men with an undying rage" — is by now incontestable. Must-read: Meredith L. Patterson's Medium essay outlining her own experiences, and rejection of Kane's entitled self-absorption:
    I have since been made painfully aware that my experience is atypical. Every time, it has been a woman who has done so. Every time, it has been a lesson in how the woman I am talking with expects the tech world to relate to her and other people like her.
    After proposing and implementing a feature to an open-source project, she subsequently learned that the developer's list had a brief discussion of her proposal.
    There had been interest, but one of the committers had dismissed the idea out of hand because a woman had proposed it. It was the funniest thing I’d heard in months — I literally doubled over laughing at how nonplussed he must have been to see it not only implemented, but implemented to rousing success.
    Whether he intended this as a snub or not, she didn't take it as one at the time. This, from Kane's perspective, turned out to be a huge mistake, because "talking about my overwhelmingly positive relationship with the tech community is nothing more than a callous announcement of 'fuck you, got mine.'" That is, she was too busy doing to worry about the possible social implications of some guy's offhand comment.
  • If there's a one-piece takedown of Kane that warrants deep reading, "The Madness of Queen Shanley" appears to be it, providing as it does a significant backgrounder in Kane's dysfunctional, psychopathic behavior. I could spend an entire afternoon reading the links there. Must-read: Elizabeth Spears' Medium interview with Kane, in which Kane even takes softball questions as raging insults, and her editor Bobbie Johnson's followup outlining Kane's lunatic, paranoid response ("harassment", "coerced" among other things) to interview requests from what should have been a friendly reporter.
  • Kane confesses racism and mental illness; the obvious must-read is Amelia Greenhall's essay on what it was like to be in close quarters with someone so obviously insane. I don't think she's learned much — the end of the piece appears to be an affirmation of the sorts of things that are explicitly problematic about Kane's totalitarian brand of feminism — but it's interesting to see how very brittle the supposed sisterhood is once there's bragging rights to be established.

Wednesday, July 22, 2015

Kathryn Finney, A Less Entertaining, Black Shanley Kane

I've previously bagged on Internet hysteric Shanley Kane for her raging paranoia and entitlement, her forays into self-parody, and her editorial rejection of the very notion of competence,  but a new customer recently arrived to add to the list of individuals who believe Everything Is Discrimination, to wit, Kathryn Finney. Finney penned her tale of woe at the aptly-named Medium, as in the Ernie Kovacs sense of neither rare nor well done. Normally, I would let such stuff pass, save for the fact that she lays a broadside at a libertarianism she neither understands nor has interest in; it apparently underpins all her failures, though, and so we are left to contend with her flabby self-absorption:
The idea of forced inclusion is one that goes against the very Libertarian foundations of tech. The freedom to run your life/company as you wish without outside interference is a sacred right in this community. There are venture capitalists, who pride themselves on being free range and not monitoring their investments.

The idea that an outside group, and for the most part women, Latinos, Blacks are outsiders in tech, would exert power, even force, technologists to be more inclusive, is an idea that sends tremors down the objectivist spines of the greater tech community.

The concept of Objectivism  — the focus on individual rights, laissez-faire capitalism, and “facts” — is one that is often hard for outsiders to understand. I didn’t fully understand the philosophy and it’s impact on tech, until I read folks like Ayn Rand and David Boaz.
(Duly noted: the whiny rel="nofollow" in the anchor tag to freaking Wikipedia articles about Objectivism and Ayn Rand, as if she couldn't stand having anyone even learn about these icky things because her linking to them might increase their Google ranking. I excised it in the quoted text above, but it was present in the original. SRSLY.)
Tech is being asked to use their resources to help the runner in back get to the starting line. To be honest, most people in tech are ok with helping as long as they’re allowed to choose when/how/who to help. I’m okay with this, as long as you didn’t use public resources (roads, fire departments, or the internet itself) or take money from a VC firm that has a pension fund as a limited partner, to build you [sic] company.
So, let's decode this nonsense.
  • "Tech" = anyone with a company I feel like telling how it should be run, regardless of the fact that I have no investment of any kind whatsoever in it.
  • "Runner" = anyone who claims to have certain skills, regardless of applicability or actual competence.
 She quickly pulls out the old MUH ROADS canard —

which is pretty much a validation of the "you didn't build that" nonsense that got Obama into so much trouble back in the 2012 election cycle (though mainly with people who weren't going to vote for him anyway). The thinking seems to go, if you live in a society with roads and police, I get to tell you how to run your company. This couldn't be funnier, more ironic, or more deeply indicative of how These People Think; after all, she confesses how she was "DONE. WITH. TECH." in March of this year, thus putting to an end her own entrepreneurial efforts. It's not at all clear what her company digitalundivided does. Aside from begging for money from like-minded busybodies, providing value to customers does not appear to be one of those things. It seems a common failing, one which hyperbolic firebrand Nero Yiannanopoulos recently bagged on:
4. There Is No Evidence That ‘Diversity’ Improves Company Performance
Seriously: I am calling for someone to do a large-scale study of the diversity efforts of companies who have fallen for this nonsense so that someone, somewhere can show me citable evidence that this does anything for a company other than provide good PR.

Maybe there are some serious figures out there. I’m sure someone with blue armpit hair is brandishing them as we speak. But until a serious, nationwide study emerges that has gone through the (look away now, feminists) peer review process, this fundamental assumption of the women in tech movement remains questionable at best.

Sorry to be blunt. But a company’s obligations are to its shareholders, not Jezebel bloggers’ feelings. So it’s worth finding out what difference a woman’s presence in the workplace actually makes.
Is there some value in having mascots? That's roughly the argument Finney and her cohorts make. Yet despite the fact that there are encouraging signs regarding getting more women involved in programming and STEM fields more broadly, for many of the hard sciences (physics, math and statistics) women asymptotically approach parity with men yet never quite reach it — which suggests women are not intrinsically drawn to these subjects. Until Finney can come up with some benefit for the companies she harangues, she's yowping into the wind.

Afterword: It's probably worth mentioning that Finney's company appears to be about flogging Social Justice and not actually writing code, i.e. there is no mention of appropriate skill sets, delivered applications or websites, etc. It's all about her ego.

Friday, February 6, 2015

Is Shanley Kane The Feminist Alex Jones?

I don't know the answer to that, but she does seem to have checked off the "paranoid lunatic" box:
Hey, um, interesting. I wonder who would staff such an outfit? Ninja women? Well, we know who she wants to pay for it:
Shanley's approach for dinner tabs must be a hoot!

Probably driving their Ferraris and ignoring squeakers like you!
Meanwhile, habeas corpus?
Hmm...
The big prize remains ahead:

A deranged mind is a terrible thing to waste! Maybe I was wrong likening her to Alex Jones: this is more like the ravings of a trustafarian.

Wednesday, February 4, 2015

Strip Mining Shanley Kane's Model View Culture For Comedy Gold

Discussing my last post with a friend on Facebook, it occurred to me that any group blog that would run such an obviously self-indulgent and lachrymose whinefest would clearly have other ore to strip mine. And I was not disappointed! Forthwith, a few of the lower-hanging fruit:
  • They apparently are new to the idea that renting is not the same thing as buying, and so people can be kicked out of their apartments in favor of new tenants when rents go up. (The editors subscribe to the naive belief that "responsible" renters will check to see whether a prior tenant has been evicted to make room for them. Good luck with that!)
  • Stop Swinging Your Dicks, C Programmers! It may come as a surprise to Jean Yang that men engage in mostly pointless trash talking about programming languages, but the reason this must stop now is predictably hilarious:
  • There is also a gendered perception of language hierarchy with the most “manly” at the top. One Slashdot commenter writes, “Bah, Python is for girls anyways. Everybody knows that PERL is the language of true men.” Someone else responds, “Actually, C is the language of true men…” Such views suggest that women might disproportionately use certain languages, but Ari and Leo found in their programmer surveys that knowledge of programming languages is largely equivalent between genders. Women are slightly more likely to know Excel and men are slightly more likely to know C, C#, and Ruby, but not enough to establish any gendered hierarchy.

    A major reason to eradicate these false stereotypes is that they perpetuate biases against women.
    It's always all about the women. We esteem Linux kernel contributors over PHP slingers because of the rigor needed for each discipline. If you want to write kernel code, do that, but be prepared for the wrath of Linus along the way. And sorry, ladies, it's not about you. Like, at all. Sisyphus, please pick up the white courtesy phone...
  • Interviews Are Too Stressful, So We Shouldn't Have Them, And No Men Because They Skeer Me. No, seriously, this was a thing Anonymous wrote (emboldening mine):
    Before each interview, I was overwhelmed by one thought: They’re going to figure out that I’m a fraud. I was afraid that, if I couldn’t understand the problem or arrive at a solution, the interviewer would realize that I don’t have what it takes to be a software engineer.
    Logically, that doesn’t add up. I have a degree in computer science. Internship experience.  A good GPA. I know about data structures and algorithms. I did tech-related extracurriculars. I work on coding projects in my free time. I’m not a fraud.

    Yet in interview situations, my anxiety would get the better of me and I’d start to believe that I was wasting the interviewer’s time by simply being there, regardless of how well I performed.  Being a woman writing out code in front of a male interviewer (because let’s face it, it’s almost always a man), or worse, a panel of male interviewers, creates an intimidating power imbalance that shouldn’t exist in a real work environment, much less the hiring process for it.
    Um, hello, I thought you actually wanted a job programming? No? And what happens when you have to explain your ideas to male peers, and male bosses, and ... oh, never mind. What planet do these special snowflakes think they're going to get a job on? (Incidentally, I actually agree with the author that technical interviews are a poor means of grading potential hires, but it beats what came before it, i.e. the silly résumé dance that does nothing to assure the employer that the candidate has even a slight clue.)
  • MOAR WIMMENZ IN HARDWARE! At least this rant makes the point that hardware defines the software environment, which is true if trivial; but then, MOAR WIMMENZ, which benefit to the corporation and its customers is left, as ever, unexplored. Something, something, diversity, something, something.
  • Look, If You're Gonna Diss The 10X Superstar Programmer Idea, Maybe You Should Provide Better Data? Betsy Haibel's post purporting to debunk the high productivity of superstar coders rightly questions Sackman, Erikson, and Grant's methodology, which used the notoriously flawed "lines of code" metric, long-ago abandoned by anyone seriously studying the subject. But then having claimed to slay the dragon, she suspiciously eschews any actual better data of her own, declaring such creatures an unequivocal "myth". (A fine rebuttal that, indeed, the 10X programmer is alive and well may be had here.) She later whips out what seems to be a running trend in these pieces, that of the horrible "imposter syndrome" monster. Is this a uniquely female problem? I would argue that it's certainly a very common one, for reasons elucidated by Katty Kay and Claire Shipman in their May, 2014 Atlantic article, "The Confidence Gap". But your lack of confidence does not a crisis for a potential employer make. If anything, it makes you sound like a problem employee waiting to happen.
Shanley Kane, the progenitor of Model View Culture, seems to be something of a fragile flower, having only recently restored her Twitter account to public visibility. Model has her precious stamp all over it. The risible fear of men and of conflict, the refusal to act like a grownup, the asinine insistence on special treatment because, somehow, diversity is better. When do they ever think of the value they're supposed to deliver to an employer?

Inexperience Is The New Sexism

I was going to leave this awful Newsweek piece about sexism in Silicon Valley on the shelf unread, but tweep @YeyoZa (who you really should be following, by the way) used it as an entryway to Shanley Kane's group blog, Model View Culture. There, we find a wholly enlightening post on Silicon Valley sexism, one which reveals much more about the sense of entitlement of the author (and idiotic reliance on credentials) than it does about actual sexism. The author opens her piece by mentioning that she went to a job fair hoping to find an internship gig, but returned disappointed.
...[W]hen I asked about internship opportunities, the company representatives said no right away, or, assuming I was a CS student, asked me “What year are you?” When I told them I was self-taught, I was out. Other companies just wanted me to sign up for their newsletters, just a cheap marketing strategy, or a way of being nice. People weren’t interested in reading my CV. Out of thirty copies I had printed out, I gave out two. Some people advised me straight away to try “one of those programs designed for women.” They didn’t even listen to me. They saw that I was a woman, a beginner, looking for an opportunity to learn, and clearly not someone they would want to hire.
This first point is an important one, and speaks to how firms find and acquire programming talent. The people at job fairs are infrequently actual hiring managers; such people are too busy doing actual work to be bothered. So who do you find at such events? Human resources types, who are most emphatically not programmers. This is, in fact, a great example of why most of them should be fired: they simply are incapable of their jobs outside filling out checkboxes and keyword searches. (That companies persist in this behavior is utterly baffling.) And determining the difference between a good and great coder can mark the difference between success and failure; the order of magnitude of productivity differential between the merely competent and the genius has been long documented.

From my own experience, good and even great coders can come from a variety of backgrounds, not just people with computer science degrees (although that does help). I've known programmers who were film majors, communications majors, business majors, physics majors, math majors, and some who didn't even have a college degree. The best all had an ability to achieve a state of flow on the job, to see inside problems, an analytical mind married to a creative streak, and the tenacity and discipline to complete projects. And none of this has anything to do with credentials, academic or otherwise.

Which is to say, I have some sympathy for author Anna in this instance; she fights an unseen host, a bureaucracy at odds with not only her own quest to find gainful employment, but with their own companies, as well. The game is rigged against the uncredentialed. The checkbox mentality of human resources is itself a lazy way of distributing the task of hiring programmers — arguably the most important single decision a software shop can make.

But my sympathy for her plight ends there. Apparently, having any kind of requirements at all for programming interns amounts to sexism:
Being self-taught is accepted and even highly respected when you’re a white male. If you are a woman or belong to other underrepresented groups, it’s totally different. Besides being experienced you need to have a blog, website, GitHub account and contribute to open source. A recruiter once told me that if a candidate doesn’t have all of those things, they wonder whether that person is really willing to learn. That statement made me angry – who came up with these requirements? And who benefits from them?
I'm guessing, people who actually hire programmer wannabes?
Why don’t I have a blog, or my own website? Because there’s so much harassment going on nowadays that I’m actually scared to put my thoughts on the internet.
Hey, newsflash: in an actual working software development shop, you will have to propose and defend ideas from harsh criticism. I know, it's not fair to point this out, but I have had pushback on one issue or another my entire professional career. I did not crumple on the floor like a vase of wilted posies; I argued and won, or lost, and moved on. What this really exposes is an overarching sense of entitlement — hey, I have the right to never be offended or hurt — and a painful lack of resilience.

That is to say, this is not someone you want on your dev team.
Why don’t I contribute to open source? Because I tried, and people were unwelcoming and even cruel.
Hm, I think I've heard that before. Yes, it's true that open source is rife with people who refuse to suffer fools (and individual definitions of "fool" can be the subject of much heated controversy), not to mention have a distinct lack of tact. But neither is everyone Richard Stallman or Linus Torvalds. My advice here would be, find an itch and scratch it, i.e. start your own project. (Of course, another possibility might be, you're just not that good. Gross incompetence gets found out pretty quick when it's on public display.)
I do have a Github account. People expect you to have one, so they can see that you can “actually code.” But while your GitHub account shouldn’t be your resume, a lot of recruiters think it is, even though I am more than my GitHub account or resume. I organize free programming workshops for women. I run an interview series about women who code. I try to learn new things every week. Just because I don’t have my own blog, don’t contribute to open source and don’t own fifty GitHub repositories doesn’t mean I’m less driven, can’t code, aren’t talented, aren’t willing to learn nor willing to share my knowledge.
There's enough entitlement here to drain a trust fund. First, you should be grateful that a potential employer wants to see your Github code; its presence alone means you've cleared the first hurdle. Second, I thought you wanted to be a programmer, not an organizer of seminars. Who gives a damn about that? I mean, it's nice and all, but what value does it add to a potential employer? They are supposed to hire you to write code, so why do you object to showing that you can? And actually, yes, your Github code is the strongest part of your resume: it is what your employer wants to see. What does your code look like? Is it well structured? Does it contain meaningful comments? How do you approach decomposing a problem? What is your approach to unit testing (and if you don't, what the hell is wrong with you)? There's simply so many questions your code can answer that an interview will necessarily miss, it's outrageous for her to take this tone. I have to conclude that this is a person who simply isn't as into coding as she claims to be. Why so defensive? I think we're about to find out:
And trying to live up to the expectations of recruiters means I mainly do what I would call “resume driven development” in my free (and unpaid) time: I work on things that would look good on my resume, that people would like to see, that “prove” that I can code, not things that I actually really want to do or enjoy.
Okay, well, then. Speaking as someone who worked for the better part of a year, uncompensated, on a project that later became an interesting (and remunerative) day job, let's unpack this nonsense: it's really saying I don't like programming enough to do it for free. There are an awful lot of opportunities out there that start as unpaid gigs which later turn into full-time employment. And the fact that she declines to actually work in her free time on skills that would be useful to prospective employers tells me a whole a lot more about her bad attitude than it does about those mean old employers. Her inexperience and apparent refusal to better herself (because the work isn't intrinsically rewarding on its own) are, in her warped view, really manifestations of sexism:
My boyfriend at that time was an experienced software developer, with two CS degrees. He attended the job fair with me — he wasn’t looking for a new job, just supporting me and scanning the market to see if there were any interesting opportunities. His resume was great, he got several job offers, people wanted him. My best shot at scoring an internship would have been if he had made a deal with a recruiter: he would accept their job offer, but only if they gave me a chance as an intern too. It’s a humiliating experience to witness that people have so much respect and admiration for an experienced male developer, but there’s no place for you because you’re female and a beginner.
How many years had he been writing code to get to that place? Did he do it for free? In high school and college? (We know the latter is definitely true.) In which case, wasn't he paying for the privilege to write code? Instead of bucking up and learning what employers demand, she insists they should pay her for what she knows now, regardless of whether it's a good fit. Inexperience: it's the new sexism.