Eleopteryx
Joined 15 years ago
Joined 15 years ago
I thought it wise to try this strategy when looking for employment, but I think it actually works against me in that case. If the employer knows I'm black then they can filter me out from the get-go and save both of us time rather than be dragged through a pointless interview process. It's hard to really quantify the exact degree to which my race is a detriment to how I'm perceived, but I sense it often enough to know that it's there in some capacity.
But you didn't get a cut of the $300m.
So you feel confident in asserting that, at the time that the person made that tweet, the quality of the Python code that they shipped was poor, or it took an inordinate amount of time to produce? All because they had to look up len()?
These kinds of anecdotes make me often wonder if candidates are "disqualified" for far more superficial reasons, and if interviewers hone in on pedantry like this to legitimize their reasoning perhaps even unconsciously. I have trouble believing most candidates wouldn't make at least one trivial mistake of that sort and I am equally reluctant to believe the same interviewers would disqualify any given candidate for a mistake so trivial.
Well, Twitter is Twitter. But Twitter is probably closer to a message board than it is to a phone call.
The aforementioned question is the only point I should really care about. If a book is harmful to a publisher's brand because of social/PR/profit ramifications, then it makes sense for them to drop it. That's not a free speech issue. If the barrier to publishing the book is legal, that's worth discussing. But beating me over the head with "but my books's not even racist tho!" isn't really getting to the core of the issue at hand.