I think the author is attempting to make the very valid point that not all good programmers can be expected to be giving freely of their non-work day time.
In short -- life happens but then the jobs dry up and good talent is over looked or lost.
I don't think even companies that "require" a strong GitHub portfolio are saying that they're not filtering out good or great programmers. It's about signal and noise.
If you are hiring for a senior development position and you have a filter you can employ that will cut out 90% of mediocre or bad programmers (or perhaps more importantly make it much easier to identify them), but will also cut out 40% of good and great programmers, it's not a foregone conclusion that you shouldn't employe that filter. If you still get enough resumes to make a decision, you've just decreased the odds that you get a shit hire by $MATH percent.
If social justice is something you care about you probably don't want to do this. If building good software is something you care about, you probably do. I think most here would agree that a random developer with a large body of public OSS contributions is probably "better" than a random developer without. I say that as someone who has pushed to a public GitHub repository probably four times in the past two years.
But, unfortunately, even mail from a properly configured mail server on properly protected domain will still end up in gmail users' spam boxes by default. Domain and server rep systems are a bear to work with.
The encryption is really quite good. It's actually very rare to have a problem with the crypto. Compromise of the trust network is much more common and is really the problem with today's crypto systems... read a bit about superfish for a good news worthy example of abuse of trust.
When reading the https gov doc -- it's very important to remember that the government runs its own CA.
Superfish was certainly a huge abuse of the trust network. However, if we look at other recent SSL vulnerabilities: Heartbleed, POODLE, FREAK - most of these are all dealing with flaws in the encryption (some directly, through most with the use of side-channel or other clever attacks).
We also know that the NSA is saving encrypted messages for mass decryption in the future. New technologies like Perfect Forward Secrecy (PFS) can help eliminate this issue. I think that fact that nearly 100% of servers were still allowing SSL 3 up until the POODLE attack a few months ago highlights how poor most SSL configurations are. Unlike the trust network, which has infrequent but serious breaches, the encryption side seems to be poorly implemented almost universally.
However, unlike Superfish, which we know affected thousands, alot of these other SSL vulnerabilities are usually just PoCs...
Freedom is an old idea. But somehow it never seems outdated. So, put down the iPhone and pick up the GNU Manifesto and enjoy software freedom -- as good as it is gnu
I agree. If you have more than one child, one parent's salary will go directly and entirely to pay for child care. It's also likely that one parent will need to work fewer hours and be available to drop off / pick up / emergency pick up the kids at day care -- which means at least one parent will need to be partially not working or at least not advancing in his/her career.
However, raising kids is very difficult and emotionally draining. Personally, I feel parental involvement is much more important than whatever might have been called a middle class lifestyle.
wake me when the clickbate is over.