skysight-inc/HackerNews huggingface dataset:
So quotas are terrible, yes.

But what if there are still biases in hiring? That someone sees a woman and assumes this or that about her based on gender alone?

My own experience as a transgender person is that there are people who, as my gender presentation has shifted, really seem to view me as less competent. Not in a "girl's can't code" way, but like steadily viewing me as more junior, needing more hand holding, giving me simpler tasks, that kind of thing.

It's subtle enough to make me constantly second guess myself, but it's noticeable.

It happens in interviews, too. It's very easy to rationalize biases within certain bounds. Those kind of things - and toxic environments - are what needs to be corrected most in today's tech workplace.

Of course correcting toxic environments early in the pipeline would be the best, because then the men that share those environments don't normalize them, either! But it's not fair to ignore the adult realities of the current working world and just dump all the blame on the early part of the pipeline.
Show HN: Chrome Extension that turns highlighted text into a Screenshot
"United Kingdom Royal Navy aircraft-carrier Her Majesty's Ship (HMS) Queen Elizabeth"

FTFY

If "HMS" is ambiguous, than [surely "carrier" is too](https://en.wikipedia.org/wiki/Carrier).
Experience is a good teacher. Dalrymple remarked on this in _Utopias Elsewhere_ -- how it sometimes seems that every society has to learn that Communism won't work the hard way.
With the current system there's no way to know which supplier is a bad supplier: there's just a bucket of mixed legitimate & counterfeit inventory.
The default for me is definitely not to use them, but if there is info that will vindicate the glasses I'd like to find it.
Thats actually a really good point, food forthough. Thanks for that.
You don't sound curious, you sound angry, as if you somehow already KNOW the answers to your questions. Do you feel highly certain that she is lying?

To understand one's mind, you should observe it.
That's a big distinction though. I don't think Google has the obligation to make sure users are educated and informed. The deceptive practice of Facebook with Onavo is what people object to.
My god. This website is full of web script-kiddies.

I've run into this need at least a dozen times.
Haha I have the same question. Until self driving cars are common presumably, but I think a lot of people are deluded about how soon that will be.
And yet, if you could have what you want, would it actually be faster?

The costs of synchronizing mutable data between cores is surprisingly high. Any time your CPU thinks that the data that it has in its cache might not be what some other CPU has in its cache, the two have to coordinate what they are doing. And thanks to the fact that Python uses reference counting, data is constantly being changed even though you don't think that you're changing it.

Furthermore if you throw out the GIL for fine-grained locking, you then open up a world of potential problems such as deadlocks. Which look like "my program mysteriously froze". Life just got a lot more complicated.

It is easy to look at all of those cores and say, "I just want my program to use all of them!" But doing that and actually GETTING better performance is a lot trickier than it might seem.
If you prepend "facebook.com/l.php?u=" to a wsj link, it will let you read the full article. Like so:

https://facebook.com/l.php?u=https://www.wsj.com/articles/fa...
If "subliminal biases" is a reference to "Implicit association" and the IAT-- IAT has lost it's scientific footing. The problem with it is that: Just because people have Implicit Associations doesn't predict that they will act in biased way.

Scott Alexander (penname for a psychiatrist) wrote about it here. http://slatestarcodex.com/2016/08/25/devoodooifying-psycholo...

> Implicit association tests probably don’t work (1, 2, 3, 4). That is, people who have “implicit racial biases” according to the tests are not more racist in everyday life than people who don’t. If this were true – and if it reflected a general failure of implicit racial biases to affect explicit actions – it’s hard to overestimate how much it would change psychology. We wouldn’t have to worry about how the wrong character on TV would accidentally bias people toward having certain stereotypes. We wouldn’t have to worry about subconscious racism affecting hiring decisions even among people who are trying hard to be fair and neutral.

(All PDF downloads)
- 1 http://www.law.virginia.edu/pdf/faculty/reassessingpredictiv...
- 2 http://www.academia.edu/download/41431928/Reassessing_the_pr...
- 3 https://www.researchgate.net/profile/Frederick_Oswald/public...
- 4 http://onlinelibrary.wiley.com/doi/10.1111/sjop.12288/abstra...
AIUI the "Limited" company in the UK limits a shareholder's liability to the value of the shares they hold - so if you hold £1M of shares that's your liability. I assume it works similarly in USA?
Unfortunately, this particular review tool was an internal utility at my previous employer. The only thing it could do was highlight changes in word documents. You could compare patch sets. That's all. And it was a review tool. Git itself still treated docx files more or less like binaries. The advantage was we could use word documents instead of markdown files, usually people would embed visio diagrams inside design docs etc.
Depends where you live. In London, Google Maps makes tube stations obvious with a big London Underground logo. Apple Maps gives them a tiny purple icon that gets lost in the noise.
A Brief History of Women in Computing – Hacker Noon
Perl 6 is a spec. The current Rakudo implementation is being focused toward sped now that the spec is stable.
> In Europe, fees are limited to
> far below that, and the
> European debit cards are
> limited to below 1% in fees.

I have frequently seen this claim made (that European credit card fees are low), then when I go and investigate it, I discover the source is referring to Europeans limits on interchange fees, not the merchant fees which dominate the cost of accepting credit cards.

In the end, I always find the costs are broadly similar in the EU and the US.
For instant.io, I don't think there really is a difference, other than that I can get people who don't know what a torrent is to download the file. And file.pizza doesn't use WebTorrent at all, it's just a plain P2P transfer over WebRTC.
[Itty Bitty Ship](https://books.google.ca/books?id=7VqK0UdKHswC&pg=PA62&lpg=PA...)
There are states in India governed by Communist Parties where the people/society are not following a communist structure
Launching a New Home for VR and AR in London’s Olympic Park
"...the fact is that virtually none of the software engineering we do in the industry --- very much including most of the work done at Google --- requires a college degree in the first place."

That's really true of any job where a degree isn't a regulatory requirement.

I think the problem with Google's hiring is less that they are hiring mostly people with degrees and more that the hiring process is a hyper competitive, stressful, multi-week long gauntlet.
AFAIK boolean circuits proofs generally don't relativize, so there's no need to discuss that.
> the only known occurrnce
> You give 100% of what you have for free [...] everyone's assets rise

...same as mathematics and most of sciences, food recipes, spoken languages, traditional music, dance, sport and game tactics...

As well as everything else, for thousands of years, before copyright was invented.
Yes, multi-processing is much easier anyway. Not to mention how complicated, not backwards compatible and thorny trying to get rid of the GIL is...
> We showed the above to playtesters (kids and parents) who told
> us what we didn’t want to hear: the game looks complicated.

That's because real programming is complicated.

Software systems, with billions or even trillions of switch points, are the most complex things humans have ever built, by far.

We have tried mightily, for many, many decades, to make programming simpler and more accessible. The problem: instructing a computer precisely and unambiguously what to do means you have to precisely and unambiguously specify...what to do! There's no getting around it, just like there's no way (yet) to write a novel without choosing words and pushing letter keys.

The graphic approaches quickly get tedious beyond toy examples. Graphs are fine for telling your Lego robot what to do, but with the Web and app store overflowing with cool apps, the bar for grabbing and keeping a would-be programmer's attention is now quite high.

My bet: non-programmers will "program" at scale when where's a fundamentally new computing model. Machine learning & deep learning are the most promising for this, I think: instead of telling the machine precisely what to do (and how), you show examples of the behavior you want and give feedback when it's wrong.
> Most importantly, though, the only contribution this post makes to the discussion is to add "I'm a woman and I agree with one side of the debate" to the mix.

If you've paid any attention at all to the conversation around this (or any other diversity issue), you'd know that _tons_ of people care about this. There are multitudes out there who are unable to rebut an argument objectively and have to fall back on "all we have here is men talking about women's issues" or "no women in tech agrees with this viewpoint: that should tell you something".

For anyone intelligent enough to consider an argument on its merits, this example isn't useful, but unfortunately this type of conversation is always dominated by those who aren't.
>What exactly does it mean to "lack energy" and to "drain energy" from other people?

Yeah, it's annoying that she's forcing readers to interpret that. I would guess that she means that they weren't able to perform their job responsibilities adequately, and others had to pick up the slack.
Redis could help. Obviously not perfect for every use case but covers many of them.
I doubt that you can say "I like you" also. Way too direct. "Gut schaust aus" is more typical
A carrier battle group is more than powerful enough to control both ends of the canal for the duration of the trip, and I seriously doubt that Egypt (or any other country) would want to cripple an economic engine as large as a canal unless they were directly involved in the war in question.
IMO, Nature is not a representative case. In my area, editors are typically academics, none of them I know receives payment for what they do.

As an example, take a look at the 34 editors of IEEE Transactions on Network and Service Management, all in academia or employed by a third party:

http://www.comsoc.org/tnsm/editorial-board
All markets frozen on Bittrex – wallets still online
Coding is like describing a trip to the grocery store in 100 pages.

"He stood up, he walked forward 10 paces, he grabbed the door, he opened the door, he walked through the door..."
Would You Watch Someone Play Video Games?
Motivation for removing the GIL is basically that when people hear about it they go "hmmm that doesn't sound good". Obviously many applications have been written in GIL languages and there aren't really many practical problems that can't be overcome easily.
BEST Sushi Spot in Los Angeles
Sayre's Law: "academic politics are so vicious because the stakes are so small."
I think it's more like a different type english.

You express the same types of concepts, but you break them down into very small parts and than build up the argument comprised of small parts.

Like instead of saying "the bike went forwards" which is very conceptual and requires a lot of background understanding of bikes and physics, you describe a bike consisting of wheels, a frame, a steering wheel etc. than describe the action of moving in a direction. finally you apply to action to the bike.
"we got responses that estimated ages 9, 10 and up- "

The point is text looks too complex for younger kids. 5 year old won't sit down for a few hours and figure out things. He will just get bored.
There seem to be a lot of naysayers in the comments about removing the GIL. Multiprocess parallelism isn't always appropriate, so I find this to be a very promising change that will definitely make me want to switch to PyPy. Here are the use cases I've found multiprocessing to be inappropriate:

* High-contention parallel operations. Doing synchronization through a Manager (a separate IPC-based synchronizing broker process) is of course less preferable than, say, a futex.

* Embarrassingly parallel small tasks. This is a big one. If the operation being parallelized is short, then message-passing overhead takes up more runtime than the operation itself, like a bad Amdahl's Law scenario. Shared address space multithreading solves this problem.

* Related: parallelization without the pickling headaches! Many objects can be synchronized but not easily pickled or copied! True multithreading would really enable a large amount of use cases (map a lambda instead of a named function, anyone?) since the same Python interpreter can just pass a pointer to a single shared object.

* Related: lots of libraries (Keras, TensorFlow, for instance) make heavy use of module level globals, and aren't meant to be run on multiple cores on the same machine (TF, for instance, hogs all GPU memory). Multithreading in these deep learning environments (assuming PyPy support from those packages) is useful for parallelizing the input ingestion pipeline. But this point isn't TF/Keras dependent; I can't recall other modules but don't doubt the heavy use of module-globals that's unfriendly with fork()-ing, especially if kernel-related state is involved.
> ...I meant senior in terms of skill level, not in terms of age...

No worries. I understood your meaning. I also meant that. I meant that hiring managers, in my experience, are more likely to give an outright "no" to an underqualified senior person than to offer them a junior role.

If the person took some time off, decided to switch industries, decided to switch specialties, or just figured out they were in a rut, giving them a junior role and letting them work their way back into an expert role should be a consideration.
I dont think this is true. There's a reason fresh engineers are paid so much, they are almost immediately valuable.
FileDepot is an open-sourced and self-managed file storage API service. (WIP)
NASA JPL's own website for this is a great place to keep up with developments:

https://saturn.jpl.nasa.gov/
Looks like .NET Core 2.0 was just released today, so guess it was more like a 3 day difference instead of a month :)
Yes, different languages make you think differently. Some things are easier to express in one language than the other.
https://books.google.com/books?id=V7wt3Sqj_X8C&lpg=PP1&dq=su...

"Subliminal: How Your Unconscious Mind Rules Your Behavior"
By Leonard Mlodinow

...
I'm involved in one and I can guarantee you that it's about 1000 times easier to blog about the issue than teach programming principles to kids.

My average student is a 14-year-old black female who wants to learn web dev. It should go without saying, I've not seen even a hint of ability difference based on gender or race. We cover JS as well as HTML/CSS -- this is not a design class, but a real development class where kids are writing native markup and code.

The program is free and held at the public library. All students are there because they want to learn. I thought some might come due to parental pressure, but I haven't seen that.

It's exhausting and rewarding.
Tried many ways of remembering it, gave up and decided a more reliable workaround. I don't know why I find it so hard to remember.

Then again I've found an even more reliably workaround by not writing much C these days.
Why we're writing our own distributed queue: introducing Bee-Queue 1.0
It's a series of tools and components required to fit certain related theories?

In carpentry you have many standardized off-the-shelf tools and components (hammers, nails, windows, tiles, dimensional lumber) and you have an almost endless number of ways to combine them. You can also create your own tools and components (which is harder). You also have some pre-determined guidelines that are meant to protect/regulate things so that they're safer and easier for a wider audience to live with, maintain, and edit (building codes).

Any of this stuff will work together as long as you stick to the constraints of individual objects as they fit into the laws of physics (a component can only bear X load in Y configuration).

The concept of "properly" is a bit varied. I can build a house with mud and straw and it's a "proper" house in some parts of the world... but it might kill me in an earthquake. This might be due to a pre-determined assessment of earthquake risk, or it might be because of limited knowledge and resources available (very common in coding, and often OK in small scale scenarios).
The pipeline is a huge problem. The numbers just aren't there currently to support a 50/50 diversity goal. It is far from a copout. It is addressing the problem at the source.

The real copout is is saying that much of software engineering does not require a degree. That might be true in a very narrow sense as far as computer science degrees go. But people still need education and degree or certification programs. We don't need a lowering of standards or removal of standards that is the copout.
Yes, thanks for updating! Looks like it was a 3 day difference instead of a month. Now I really need to scramble to get my libraries updated :)
So how would you counteract that stereotype/bias?

Author would suggest lowering the bar [for women] would only reinforce such stereotypes, do you agree or disagree?
"I'm not saying it isn't useful - I'm saying it's not interesting "

Then you are doing it wrong :)

"(and I'm talking about the act of parsing, not the algorithms as applied elsewhere)"

I'm not sure what this is supposed to mean. It sounds like you are trying to separate parsing text into ASTs and parsing flowgraphs, so you can claim one is boring, and the other is "algorithms as applied elsewhere". There is no such separation.
We just happen to name variables a little differently so it doesn't quite look like "figure out if this one parentheses matches this other one". But it is the same algorithm.
If you are trying to separate parsing as the thing that happens that makes an AST, that is not the only thing that is parsing. Yes, some books colloquially separate phases like that, but it's silly.

"Think about this: you start learning compilers, you spend months on parsing, and after that what do you have? Nothing - you "compiled" stuff into an AST. "

You are definitely doing it wrong. The same parsing of a grammar you taught someone to make an AST, you can now say "we can apply a slightly different language grammar to the AST and generate machine code", or "apply a slightly different language grammar to the AST and parse out flowgraphs and statements"

etc
parsing isn't just take a bunch of text, turn it into an AST.
The fact that a ton of people think this is one reason there are so many crappy little compilers that never go anywhere :)
Lessons from My Mistakes: Start with MySQL
A truly revolutionary idea in this era of authoritarian social justice causes.
No, definitely not. To me it is about the logical flow of thought that is put into a structured format. That might sound like spoken language, and to a certain extent it is. But code is more than just that. It is precise. There is no ambiguity. There are hard rules. A violation of format/structure/syntax is not allowed.

Most importantly, logical errors result in unexpected behavior. In most spoken language, someone could be an absolutely terrible speaker and can still manage to get the idea across. There is no code equivalent of saying to someone, "I dunno, it's hard to explain, but you know what I mean, right?"

I would say the closest "language" that code can be related to is legalese. It has definitions and exceptions and legal agreements tend to conform to standard to ensure their validity and enforceability. A significant error in this regard would void the agreement, or at least part of it - similar to a compiler error. Also, I like to think of good code being a battle plan where you want to make sure no one is able to do anything you don't want them to do, even if they do something unexpected or deliberately try to break your code. You try to think of every scenario that you can possibly encounter and you code for it. This creates a defense for your code. Legal documents tend to be created with a similar mindset of protection and survival.
https://www.scientificsonline.com/shop/solar-eclipse?Page=1

Just bought 2. 30 dollars (5 each, 20 dollars for fast shipping). Might not even need them as we have welding helmets, but I don't want to screw around concerning my eyes. Accidently got myself with a camera flash once, that was more than enough.
Not knowing Swift, I would've guessed something similar. But that hardly makes it a suitable language to dump on kids. For an educational language, you need to start off small with intuitively sensible constructs, and build up.

You can move towards that syntax, but you can hardly start there.

EDIT:

Actually, I'm going to make a stronger statement. You shouldn't make an educational video game, and particularly an educational programming game, until you've read Mindstorms and learned what Papert and others studied last century.
This seems so wacky to me. Are you guys seriously going to start sending thousands of dollars in currency through some random website with a marketing page and a blog?
Maybe you can address the issues instead of playing armchair psychologist.
> Nobody can reasonably believe it's realistic to expect parity in hiring in the immediacy, and all the available evidence suggests --- like you'd expect! --- that Google doesn't expect that either.

You're clearly entirely unaware of the context of any of the diversity conversations that have gone on in tech in the last 5-10 yrs, including those internally and externally at Google. You're correct that expecting employer demographics to immediately exactly reflect US population demographics is stupid. You're wildly incorrect that it's uncommon.

As just one example of the top of my head, Google released their diversity a couple of years ago and coverage was almost universally: "Google has a serious diversity problem", "Google needs to do a lot better".

The actual gender numbers? Non technical employees were split down the middle and technical employees almost exactly reflected percent of CS degrees by gender.

Something isn't a straw man if it's an argument that's constantly made and carries a lot of influence.
The fact you can intermingle .net core and .net framework libs and VS will handle the interchange for you now seems like a really nice addition. I haven't had much chance to play with Core but knowing they've simplified things has me anxious to give it a try.
I can't speak for Google, but I work for a large SV company with an aggressive diversity program, and the goal is to hire to match the demographics of the pipeline of qualified candidates, not the population at large.
Learn Ethical Hacking Course: Footprinting Theory
All: We've banned this site and this account for using a spam service to buy upvotes. Obviously that is a capital offense on HN. There's no issue on which the community feels more strongly.

I wish everyone would realize that when they do this, they leave obvious trails in the data and so it is not worth the risk.
Investing is about creating assets and having a diversity of assets. Assuming that $100/month is one part of your expendable income that you have considered for crytocurrency - you are in good hands. However if you are putting 100% of your expendable amount in cryptocurrency - do revisit other options.

Do also go through https://www.wealthfront.com/questions and other finance portals to see how they allocate your investments amount based on risk profile, age and goals.