zephharben
Signed, a Jew with a personal background in these matters.
Oddly, DataGrip doesn't provide this option.
We're talking about an open source project used by millions of people that has gotten CONTINUOUSLY better over the course of decades - to the point where it is now - arguably - the best of its kind.
Given this track record, I think postgres devs are entitled to use whatever management-speak euphemism they like. In this case, the idiom's original meaning/intent seems apt.
Instead, it's a matter of understanding that most attacks involve several pivot points; and that these pivots are possible because we treat internal networks as if they are "safe spaces" where we can let our guard down.
That's why the SPF check doesn't fail.
However, in the year 2018 I'm shocked that Gmail would put messages that fail dmarc into users' inboxes.
- "by definition, PoC can't be racist" - e.g. as an argument to shut down complaints of "reverse racism"
- white people must listen to PoC's before they can engage in discussions about racism (e.g. - don't force PoC's to engage in the emotional labor of educating you)
- you can't make assertions about the experiences of PoC/women/trans/non-binary people if you haven't lived as one
etc.
I'm not making ANY judgements about the truth/validity of the aforementioned "rules of engagement".
I try to follow these rules when talking about social justice issues. It's no skin off my back - but it certainly adds some limits to the types of conversations I'll participate in, and the kinds of things I might say. I don't think there's anything wrong with that - as long as I don't slip into outright dishonesty as a result of these constraints.
I think some of the backlash against social justice by conservatives comes from the belief that these kinds of constraints are unacceptable, and are concocted by stupid, illogical people.
I love jq, and use it more often than JMESPATH. However, recently I've noticed that I arrive at "the solution" I need more quickly with JMESPATH.
In retrospect, JMESPATH's documentation and examples have been more useful for me than jq's (docs/examples).
For organizations that are closely aligned with humanitarian causes (e.g. health projects in the developing world), I've noticed a much higher gap, presumably because these organizations are able to attract talent that's more passionate about the cause/willing to accept lower compensation.
I wasn't delving into the merits of diversity - I believe in it; I'm seeing it put to the test every day at my company, and I like what I see.
> it doesn't follow that maximizing diversity is therefor an imperative for companies that want to have world-class teams.
Diversity isn't about addition/subtraction, nor is it calculus; it's not even sociology, macroeconomics, or socioeconomics.
Diversity is about adaptive systems.
> In fact diversity seems to be orthogonal to competence.
I'll concede this point, but only with the substitution of "productivity" for "competence". Homogenous teams can outperform diverse teams, IN THE SHORT TERM.
Diversity may lead directly to inefficiency and conflict. In the short term, these are painful inhibitors to productivity.
In the long term, diversity of backgrounds, capabilities and perspectives - properly aligned - can be a huge asset.
If you are building a new company, and you want to beat the world, you'd be foolish to hire a bunch of people who think about things the same way that you do.
Hiring managers and executives should use all of the tools at their disposal in the context of recruitment and hiring - including moral and ethical judgement.
Setting moral responsibilities aside - if you want to hire talented, passionate engineers like me, you will get serious about building teams with people from diverse backgrounds.
I'm glad to see projects taking a simpler approach to zip apps - pants makes sense if you're trying to package legacy apps with huge sets of dependencies, but it's overkill for smaller apps.
However, the author needs to add some test coverage before I'd feel comfortable contributing or using it.
It's important to recognize that private capital isn't simply "rich people playing with their own money". The lack of transparency and accountability in this sector is going to have negative consequences.