skysight-inc/HackerNews huggingface dataset:
While I think the article is primarily a collection on anecdotes the number describing the issue are amazing:

> Women make up 20% of engineering graduates, but it’s been estimated that nearly 40% of women who earn engineering degrees either quit or never enter the profession. Clearly, some elementary and high school reforms are working, but those at the college level are not.

There is obviously a mismatch. I'm wondering however to what extent the issue is at the receiving engineering job market end and what can be attributed to the pushing school side? A lot positive can be said about scholarly achievements of women but we all know there always has been limited correlation of grades with any genders success in job. Maybe some women are directed towards engineering, succeeding initially when they are faced with school type exercises? Maybe the selection at university is tuned to be hard for men and works indirectly as a selection for other traits than math?

In any case considering the magnitude of numbers I'd like to see a breakdown of where women exit. University, first year at job, 5 years and after first child. The article does not help here.
The people I know who use desktop Linux love their Linux rigs a whole lot more than my Windows and Mac acquaintances enjoy their computers--which in many cases just borders on tolerance, especially with Windows 10. Maybe software needs something beyond market share, sort of like what Bhutan did with Gross National Happiness. We'll rank products based on how much people enjoy them and then see who's the dominant desktop.
If you don't buy anything, just go past the queue at the checkout line.

> There was immediate pandemonium,

Try to sit in the front seat of a cab in the US, which would be typical in Germany - in the US the cab driver will yell at you, or show his weapon.

Traffic control by the police. Try to reach into your pocket. Immediate pandemonium. In the US, not Germany.

Each country/region has its rules. You have learned yours. In a different country there are other rules.

Surprise: Germany has other rules than the US.

Drinking alcohol in public places? In the US? Not really. In Bavaria you would drink beer at work.

Driving speed limits? Strict in the US. Welcome to the German autobahn. To make it possible that you can drive without speed limit in parts of the autobahn, you have to follow other rules - like using a car that actually is safe at higher speeds.

> I'm curious where the German propensity for strict organization,

That this is specially German is a myth. It's also a widespread myth that this is everywhere in German society. Take for example childhood: much less strict organized than in many other countries. Children walk alone to school, take the bus, the train. They are much less drilled than in some other countries.

> rule following, etc, comes from, and how far back it goes. The posted story seems to suggest it comes directly from WWII,

Order comes from the Kaiserreich. Local order came before the Reich.

Every country has its order system, you have to detect it. In the UK you see the people neatly line up at the bus stop. There is a lot of order in public transport. Even more so in Japan. In the US the access to public underground transport is through gates. Something you would not find in Germany - access is open. As a German I find it very depressing to go through steel gates into the public transport system in the US.

>since the East Germans don't seem to have the same attitude.

They have. But it shows in slightly different things.
Pyract: a new way of writing Gtk+ applications
I imagine the conversation going on the lines of:

Facebook: In the week we exposed the user to the add, the user posted a picture of your product. We made that sell for you!

Advertiser: Say no more, take my money!

Facebook: (smiles smugly)
I love spring boot. And I like golang as well.

Spring might look bloat in the start, but it's powerful. At present there's no framework in golang which has so much power and freedom...
> Just wanted to say that was an awesome essay!

Thanks! Honestly, that makes it all worth it.

However, I don't feel crucified or a victim of groupthink, I put this on the web and anyone can feel free to agree or disagree. I think there are many people in the HN community that agree with me. I find there are some very valid criticisms here and more than anything I simply want to inspire and encourage debate on these issues. I'm not the best writer, and I certainly added a lot of rhetorical fluorish to this essay, but in my mind it was necessary to underscore how casual off-hand assertions like "the best programmers are libertarians" are also rhetorical tactics meant to align people on what their political beliefs should be.
I was being glib, but I do want to clarify more seriously: the federal environment was neoliberal. States that have succeeded have recognized that excess and written policy compete directly with states on worker stability.

In a strict sense, you're right. As a consequence of federal policy, it's inevitable that some states would try these strategies. They're the ones that the less successful states point at and say, "smug elites". My point is that their state legislature did very little to protect them. I realize that I edited a paragraph to say "embraced" to remove the remainder of the sentence to remove the words "as opposed to gamed the system", which is what I consider several blue states to be doing.

In this sense, neoliberalism has enabled an apples-to-apples comparison in an increasingly open border economy. Some people even argue that this was the ONLY way to get any sort of test (which is what I was alluding to with my prosperity statement, I don't buy this).
Voting App: Who Wins Super Bowl 51?
An HTML version of the second edition, and links to various translations of the third edition are at http://www.tasrt.ca/
It's the same cognitive load, really. Instead of deciding how to best propagate exceptions, you're now deciding how to best propagate the error value.
Concierge access is a business model largely dependent on the SES of the community the doctor is located in, and his personal charisma/following. It's very, very poorly correlated to physician quality.

Access tends to be a lot better, but only in those practices that are 100% cash. Those practices that try to "transition" or do a mixed customer base tend to be the same as all-insurance practices, since they fail to transition operations/processes towards the cash-based context.
Also, XP was released in 2002, so it should work rather well on the previous year's hardware...
The hiring process in 2017 is:

1. First CS exercise - phone screen (1h)

2. Second CS exercise - phone screen (1h, optional)

3. Onsite (full day of CS exercises on a white board or on a computer)

4. Sometimes you get an extra coding assignment when they still can't make up their mind

What I'm saying is that all we need is step 4 + culture fit, which could be done in one single day. So we could get rid of all the other useless steps.
It's easy to picture the current state as what will rule the future.

I doubt it. IMO, Facebook as it is today is a fad that is already cracking -- FB constantly has to adapt to retain engagement with younger people and new users.
Netlify: Learning review for our Feb 2 outage
You should probably find a new startup to join/start.
Put it this way. If you see two apples, one organic and one not, but the one that is not is cheaper, you would only buy the organic one if you believe that it's healthier, or you feel like you're doing something "good". But if you do that, you're making that decision without evidence of the organic apple being better for you. The rational decision is to pay for the cheaper one, unless you're at least consciously choosing to buy an organic apple because you believe it's a value statement.

If you buy the organic apple because you believe it's healthier than you're doing so without evidence and effectively asserting that such evidence exists. If we're to assume (and I think this is the proper assumption) that you don't have proper knowledge about the health effects, then the default choice where you're not positing that there is any evidence would to simply purchase the cheaper apple. In that case you're saying (I don't know) and taking that factor out of the equation, which leaves either price or lifestyle, which I mentioned above.

I used to believe that GMOs were bad and organic was the way to go. I thought I had to stand up to big agriculture and buy local. I still mostly try to buy local for environmental reasons (and others), but I no longer factor "organic" into the decision. You can get "organic" just about anything these days whether or not it's actually "organic", and often times it's worse for the environment.
Ruby came out in 1995, 22 years ago. It is neither young nor immature.
I downvoted you because this really has nothing to do with the article. Nothing in the article blamed white men for anything.
What a glorious time it was with that master playlist and the excellent keyboard shortcuts. I used to put it on shuffle and play a game where I'd press Next and then Pause immediately and try to impress friends by knowing what song it was within the first half-second.

You could also just conjure up any song with the "J" keyboard shortcut that would search the entire path as well as the ID3 tags. It was so good that one weekend night in high-school, my friend and I decided to put an old desktop in the back of my Jeep on foam and power it with an inverter. We ran aux wires to the stereo and I literally just had a full-on keyboard that I could pull up while driving and get any song in my library with a few slaps of one hand without looking down even once (I knew one-handed typing skills would be useful someday). (I even tried voice command with Dragon Naturally Speaking but it only worked when the engine was off.) To this day, I haven't had such an agile interface to my music. I just use a phone now but it has a fraction of my old library and searching for things while driving is dangerous, illegal, slow, and miserable.
Unity needs graphic acceleration. Of course it does not work on something like that. Use Lubuntu and it will work just fine.

XP on such machine is not responsive. Maybe it could be usable, if you uninstall half of operating system, and replace most programs (IE with Opera 12.X....). Or better is to use Win2k.

No! Lightweight Linux distro, is your best bet to revive such junk today.

EDIT: fixed typo; I restored a few netbooks in EE, but whatever.
Neglected Big Problems
but RAID by definition involves multiple supports. So it is not very practical for long term archiving.
FAKE NEWS.
But the syntax is in es2015. So that feature should be marked as NO in those tables.
Wiki: General availability	October 25, 2001; 15 years ago.

General minimum recommended for XP was/is 512MB.
Interesting project. Wonder will it include features in future which allow for higher security transfer of information. e.g not SMS
Long-awaited update for PS4 finally arrives
I'm concurrently learning Go and Node, which might not be a fair comparison but I'm going to make the comparison anyway.

Node feels like a flesh wound with delicately layered bandaids. The ecosystem is a mess, you have to jerry rig basic packages to work together, the syntax and semantics of closures and context is ridiculous, and despite that callback mania is like this cool-aid that's supposed to feel great once you drink it (but hasn't yet for me).

Go just...works.
They seem to take a lazy approach to feature development. Generics are complicated and bad, but having makeIntMap or makeStringSlice is...not great for developer productivity.

So let's special case `make()`, slices, channels, etc. so that some productivity is possible.

Then as they add library features they violate their own tenants as they find utility in these verboten constructs. Exceptions are bad...But we have panics which are in no way the same thing renamed. Never expose them outside a package...But closing an already closed channel panics. Random number generator functions panic on mundane and expected things, just like Java checked exceptions.

Example:

https://golang.org/pkg/math/rand/

```
func (Rand) Int31n

func (r Rand) Int31n(n int32) int32
Int31n returns, as an int32, a non-negative pseudo-random number in [0,n). It panics if n <= 0.
```

Standard behavior would be returning an error, not panicking,

See this:

https://blog.golang.org/defer-panic-and-recover

```
The convention in the Go libraries is that even when a package uses panic internally, its external API still presents explicit error return values.
```

It's just an inconsistent and, quite frankly, disappointing language outside of goroutines and its interfaces. Those two make it possible to be productive, but with generics for instance a whole slew of new possibilities will emerge.

The simplicity is nice, but it's too simple and too inconsistent. All the verbosity of Java combined with the impenetrable inconsistency and abbreviations of C.
Embedded designer here. Came to say RISC-V as well, but not because of performance. It will be because of price.

A significant hunk of a Cortex-M die is the ARM licensing fee. If we can drop that? That would be an order of magnitude of savings on my BOM.
Adobe to raise its prices in the UK and Sweden
How the hell can he offer anything ?He is candidate for the election to come and even if he's elected this kind of law will need approval from senate and national assembly (read not likely to happen).
Coming from Reuters this misleading title is a sad reminder of the state of journalism.
I've been researching container orchestration recently and I personally don't see the incentive to jump into containers from an infrastructure perspective. I think using packer/vagrant/ansible is pretty easy and meets my needs. The orchestration overhead for containers seems like overhead I don't need just yet. So the big question I've been asking myself is at what point will a AWS AMI be less versatile than a docker container, assuming it originated w/ Packer and I can build images to other clouds with packer.
From a developer perspective I am very excited about containers and believe local dev w/ docker is warranted.
It's true in CompSci but not popular INFOSEC. Most of them cite Thompson as original, definitive work as he likely intended when not giving Karger credit in first paper. The people discussing these things also dont know about all the attacks and solutions Karger found. If you need evidence, just compare most security-oriented VMM's to Karger's for VAX. It's like nothing got passed down. They even rediscovered covert channels in cloud VMM's around 2010 or whatever. So, I keep referencing him on topics likd these.

"Oh, and thanks for the citation about my paper on SCM security!"

You earned it. :) One thing I am still curious about was who originated the high-security techniques for SCM. Back in Karger's day, they just put it in safes on paper. Im wondering who did fundamental stuff on making it electronic and secure, though. Figure it's in your collection but asking in case you know off hand.
> Additionally, many believed that by fighting against Germany in World War 1, all German-American's had proved their loyalty beyond any more doubt.

I'd love to see a source for this. My research and interviewing my relatives who were there suggested that they were quite concerned that the germans were "hard to spot".

> Italians were a 'new' wave of immigration, pushed into ghettos due to existing social bigotry, and easily differentiated from the normal phenotypic blend of older immigrant populations that became the white American norm.

I mean it wasn't _that_ new. There was a major wave of immigration in 1910.

But bigotry based on appearance is almost always the basis of this.
Sigh. I actually had hope that IMDb would eventually fix its social functionality. That's obviously never going to happen.

There is (was?) a way to add friends on IMDb, but I found it ridiculously hard to find, and even now I can't see their movie ratings or watchlists. The message boards were stuck in the 90s, but at least they got the job done.

Maybe I should write a script to migrate all my ratings to Letterboxd...
I just read this on my Chromebook, powered by Linux.
OP never claimed there were countably many functions from N to N, only that there are countably many Turing machines which is true.

By "polynomials" OP doesn't mean polynomials over the reals but over, for example, the rationals – the point is that there's a countable subset of R that's algebraically closed.
I agree with your points. My comment was based on my personal experience as a radio amateur. When I was young, when Morse was still central to radio communications, I spent too much time learning how to send and far too little learning how to receive, such that my receiving speed is now still far below my ability to send.

> Second, effort spent on sending practice helps reinforce receiving practice.

Perhaps to some extent, but I find that I can send with much more adeptness that the reverse. This (or its reverse) may be a common experience. I think time should be devoted to both, so I think we're in essential agreement.

> It's a hobby and should be fun!

Complete agreement, and how times change. After the Titanic went down, nautical authorities promptly required that radiotelegraph sets be installed on all large ocean-going vessels. Now Morse is a diversion, an interesting historical artifact.
The original sin of the Linux desktop was the kde/gnome split over licensing. Had Linux had one good desktop, like the other operating systems, it could have had a future on the desktop.

Instead it has had a number of almost-good desktops that are still fragmented by hate and the desire to thwart interoperability. For instance, the GTK team won't fix certain bugs that affect running in a rootless X server because they can't stand the idea that you'd run Eclipse on Linux and view it on Cygwin/X.
still, it would be a very large web, large enough to encompass several families, not just one.
In fairness, it's the Mayo Clinic's enormous prestige that acts as a supplemental non-cash reimbursement to the physicians that practice there. It's, more generally, a trait of hospital systems to substitute reimbursing physicians with culture rather than cash. They get a flat salary, and in some places a volume-based bonus. In places where the culture isn't earnest, insufficiently prestigious, or both, this cultural currency falls flat and physicians (and other staff) absolutely start to suck more.

Outside of hospitals (hospitals and physicians are not equivalent; think Walmart and your local mom-and-pop shop, if you want a better idea of the relationship between the two), physicians are reimbursed directly by volume. Not quality, though - just volume.
Yes, massive increases in efficiency. A radiologist can read anywhere from 50-100 images per day (depending on modality CXR/MR/CT/etc). Voice dictation is ubiquitous and residents are trained from the beginning on how to navigate the templating software.

There are three areas that take a lot of time that radiologist would like to see automated:

1. Counting lung nodules.
2. Working mammography CAD.
3. Automated bone-age determination.

Those are the hot three topics for machine learning. Personally, I think that a normal vs. non-normal classifier for CXRs would be more interesting because you could have a completely generated note for normal reads, and radiologists could just quickly look at the image without writing/dictating anything. Of note, hospitals and radiology departments typically lose money on X-ray reads because the reimbursement is $7-$20 (compared to $100+ for MR/CT). So if you could halve the read time, they might become profitable again.

Edit: In terms of 10x, what you'd want is a system that would automatically make the reads (i.e. radiologist report), and a very efficient way for radiologist to verify what is written. It's hard to make a pathologic read, but since roughly 50% of reads are normal, you could start with normal reports.
Go is meant for distributed systems. All these companies, and generally speaking a lot of infrastructure thing is in that domain. They use the right tool for the job.
It was insinuated by talking about problems women face from peers in a field that is largely made up of white men.
> it’s been estimated that nearly 40% of women who earn engineering degrees either quit or never enter the profession.

Fantastic! That's much, much better than the 73% rate of college graduates not entering the field of their major https://www.washingtonpost.com/amphtml/news/wonk/wp/2013/05/...

Of course, maybe men in STEM have an even lower rate. IDK, and this article certainly doesn't seem to know that important piece of data either.
The desktop is dead anyway - people use phones and tablets now. For the uses that my son gives to the PC - YouTube, Agar.io and Counter-Strike - he uses Mac or Linux without making distinction
In reality Go makes it worse, if you truly keep track of all possible cases. After calling a method, in Go you have to

1) "if err != nil" after every statement

2) give some serious thought to whether the previous statement could panic or not

Good luck if it's a library call that may get updated or call other libraries !

3) Think about the non-error error cases that can't be abstracted out. Go is like C, in the sense that there is an ERETRY "error" (unsurprisingly, you should simply try again, you should NOT fail)

And there are cases where there can be an error and yet error is nil. Easy example of this would be sscanf.

And we now see practical Go code published online : how these problems are dealt with, real world edition:

1) either mindlessly putting "if err != nil { return err }", which is a very bad information-erasing exception system, or just outright ignoring errors. Don't you know you can also use "_" as the error variable ? Maybe they should make that implicit like in perl. Of course perl is likely to tell you this happened ... unlike C and Go.

(really brings back the C days doesn't it ?)

2) most people either don't know or just deny this. Thankfully panics at least do list where they occur. They also kill your program and print stacktraces. Pages and pages and pages of stacktraces.

3) very few people even know about these problems ... so they're ignored, and the standard Go tools themselves don't behave according to unix specifications.
Amazon Polly is ivona. Amazon bought them years ago and they do all of Amazon's TTS.
Annoying? That's terrifying and I'd feel terrified.
Part of that comes from the sense of ownership and the love that a tinkerer has for their projects. Not that it's a bad thing, but I think it's easy to see how that love would arrive.
Why I decided to abandon dot.net core and return to .NET Framework
Hey, the key assumption (the "identification" assumption) is in 2.4 of the paper you referred to. I do not have time to go through the notation, but it seems to be like a fairly standard "no unmeasured confounders" assumption - so you need to ASSUME that nothing influences both the treatment and the outcome you are interested in. Then, of course, you do not need to randomize, but can use observational data.

I know that Petersen and van der Laan are well-respected researchers in causality that know exactly what they are doing. E.g., Petersen has a course (I think at Berkeley) that uses causal graphs which were pioneered by Judea Pearl (see comments below). I can only second the recommendation to dig into his work.
At the risk of being downvoted, I would like to raise a topic for deliberation-

Why are some acts (driving and polluting) penalized, but other acts that also cause harm (especially to children) are not penalized?

Driving and pollution are low hanging fruit, but what about polluting water supplies? Trash, sewage, dumping, antibiotics and pesticides in food sources....

Surely all of these things are dangerous to everyones health, especially children.

Should we have facial recognition software for people walking around with bags near water sources at certain hours of the day?