rpcastagna
(DigiNotar, of course, famously gave out a fraudulent * .google.com cert and is now defunct.)
As a CA you're assuming a whole lot of liability for not that much money (not that much at the scale of even a small business, anyway), and that just doesn't seem like it'd scale to a wildly profitable venture, especially considering the kinds of people who are actually well equipped to run a CA can probably make a lot more money doing basically anything else in web security. When you add up the contingency risks, the opportunity costs, and whatever actual day-to-day business expenses, it does seem like you'd be looking for other ways to make more comfortable profits.
That doesn't mean CAs should charge more or anything, just that I could accept that SSL certs for standard websites isn't what anyone with a good vision for their business is really trying to hold onto.
A new form of literacy
Suicide Rates After Discharge from Psychiatric Facilities (2017)
Relevant bits start at page 12:
"G Suite customers own their data, not Google."
"There is no advertising in the G Suite Core Services, and we have no plans to change this in the future"
etc.
Ultimately the biggest cudgel you have to wield here is in the sales contract you're signing, but my understanding is that the baseline privacy guarantees are standard for all customers at the strictest level -- people actually opt to reduce the restrictions on their data so that new features get built with their use cases in mind (otherwise we wouldn't know what those actual use cases were).
A lot of companies use G Suite and a lot of them have very strict privacy + security requirements. This is the same platform used by fintech companies, healthcare companies, MegaCorps, etc.
Sort of a thing with all non-web-search Google products: I can't fathom how people see the $5B/quarter "other revenue" line on our earnings statements and think that just doesn't matter and somehow we have to get the "real" money from ads. We definitely did ads-supported-consumer first and we've been doing it the longest and it makes the most money, but how many email providers would kill to have half of that quarter as their annual revenue? G Suite, Cloud, etc are very real businesses in their own right and that's even while being very young and coming from a company that didn't start with any inherent strengths in enterprise markets.
The answer is no. To the point where it's actually a pain in the ass for us because developing any ML-assisted capabilities for G Suite requires us to only get training data from specific subsets of customers who are under special contract conditions.
If you buy G Suite from a reseller then they might be doing shady shit but we'd terminate their reseller account if we found out about it.
I know people like to bitch about this kinda shit on HN but honestly I and my coworkers spend so much time on protecting our customers' data from literally everyone -- including ourselves -- that I want the chance to bitch back about how hard my job is.
Find what's useful
Hospitals of reasonable size typically have an on-site clinical engineering team that handles those kinds of situations. Important (that is, capital expense category) hospital equipment will typically emit all kinds of warnings and alarms way before anything's actually a problem, because everyone would rather rely on the on-site engineering spending a little extra time silencing false positives then leave anything to chance.
Take real chances, dick
These are the risks of working at the national and global scale; they have to be there, otherwise the rewards couldn't (sustainably) be so great. Even ignoring the moral arguments, the fact that anybody is making them changes the game theory perspective as well. The only way to truly stay on top is to make sure most people want you there.
The merits of being unrelentingly thorough
Any theory of the current state of medicine that involves a cardio-thoracic surgeon feeling like they are not completely irreplaceable, one-in-a-trillion geniuses/minor deities, put here on this planet to spare us lesser mortals (as scheduling allows) seems... improbable.
I would also add that my perception from working at a major east coast hospital has actually been that hospital IT clamps down on new tools more than anyone because of HIPAA requirements, etc, that the doctors ignore/don't care about as much as they should. It's a complicated, layered system.
I'm also a software engineer at Google and I think our stock price has gone up too? I might be wrong.
Even for athletes, though, you see more simple name recognition for NBA players than for, say, NFL players, simply because basketball teams are smaller and the individual players are so much more pivotal to the team's success.
But why am I supposed to feel good about being part of that system? And who decided that was the best we could possibly do?
19 years out from the release of Black On Both Sides and still all anyone wants is to tell me to try to have some fret in my heart behind the things that they do. I mean, I guess...
The idea that people's engagement or happiness -- or even just their general satisfaction at work -- is strongly correlated to their employing corporations' success is a persistent myth in tech that I just don't understand. People hate "sell outs" and they hate themselves when they sell out for a reason. You start as someone dedicated to a craft, you end up working somewhere that pays you a lot of money to do it but without giving you the chance to put yourself into that work at all, and then you end up making soulless work that not even you really like. But it made money so it keeps going like that until it absolutely blows up and everyone has to "rebrand" or another company slips in as the rebranded form in your place.
Steph Curry is happy when the Warriors win because he's on a team that is winning by playing the game his way. If the team made him go to dunk every time he got the ball I bet his satisfaction would be shit too -- and it probably wouldn't keep netting the Warriors more rings.
Advice on “making it” in tech
In my experience, good lighting is pretty much the only thing you're guaranteed at various warehouses. Heating huge spaces effectively is basically impossible, rugs and other "soft" surfaces are out since they just wear down too quickly, equipment will be used continuously until it's simply unsafe... but you need good lighting to know what you're doing and keep yourself out of harm's way. As noted, even the parking lots and immediate exteriors will be very well lit as a physical security measure.
Bad lighting is the exact kind of thing people complain about when maligning "hot shots who think they know everything" and all those etceteras. It ends up being penny wise and dollar stupid when you factor in both logistical mistakes and pay outs to worker's comp when people injure themselves on the job. The equivalent in programming would be making all your developers use laptops from 12 years ago running Windows XP because you know someone who got you a really good deal.
From a system design perspective, being able to handle a large number of files regardless of type is an interesting challenge, as is being able to handle a large number of highly indexed text files. All three of those statistics seem potentially interesting for different audiences that might read this paper.
It's 100% a cultural difference. While you see it as personally aggressive and grating, a lot of people see "overly polite" language as a sign that you don't care about the topic being discussed and/or are trying to address an issue politically rather than by merits of a strong argument. Neither of these perceptions is really right or wrong, it just has to do with the perspective you have based on where you grew up and who you've interacted with the most.
From an engineering perspective it'd be optimal if everyone had the same universal expectations for how a conversation should be held, just like how it'd be optimal if everyone spoke the same language. People don't really work that way, though, and just like with languages we try to accommodate each other as much as possible and find middle grounds, etc.
> They would gain more advertisers paying them money to advertise with them.
I don't really understand what you're saying here. Why would more advertisers pay them money if less videos had advertisements?
Some of the comments here seem to suggest people might be instinctively identifying with Palantir when they talk about their own difficulties in trying to find qualified job applicants. It's without a doubt incredibly hard to find qualified job candidates, and there's a huge number of factors that can go into making any hire/no-hire decision, but for those very reasons these types of lawsuits from the DOL are both hard for them to win and pretty rare, which suggests to me that there's a fair amount of objectively quantifiable evidence pointing towards discrimination. I think, unfortunately, that it's much more common for widespread discrimination to never be addressed in certain companies than for the federal government to overzealously sue corporations on marginal evidence.
I don't think there's any question that Palantir is going to be ultimately ok as a company, however the law suit turns out. Even if the ruling was to wrongly come down against them, they'd pay $___ million, change their hiring processes so they're at least less likely to be sued again, and then move on with their lives as a hugely valuable multi-billion dollar corporation. Discriminatory hiring processes, on the other hand, I think need to be routed out wherever they may occur because systemic injustices ultimately hurt our society as a whole.
This allegation is very serious and I think needs to be taken seriously. When our instinctive reaction to an accusation of discrimination is that it's more than likely overblown or outright false, we're implicitly endorsing the idea that discrimination is both rare and always obvious, neither of which I think are true. I'm not ready to make any judgements about Palantir as a company or its hiring process, but it seems very likely that they (like any company) have blind spots in the way they're hiring that disadvantage some groups, especially if the DOL thinks there's enough evidence to win a court case over it. The great news for Palantir is that even if that's true, it's not an issue that really affects any core component of them as a company and it's 100% fixable with some extra HR spending.
I think the more constructive take-away from a news article like this is to think about what we ourselves do to eliminate bias from our hiring and potentially talk about what works and what doesn't. No one wants or needs us to hire unqualified candidates, but it's undesirable for us to unfairly exclude groups of qualified candidates because of race or any other discriminatory factor, both because of the societal implications and because we end up missing good candidates in a time where good engineers are in incredibly high demand. Like I said, establishing fair hiring practices is a hard problem; it goes a lot further than just trying to "do the right thing" and reaches into a lot of core parts of how we perceive the world. As engineers we constantly try to study and adjust for our imperfect brains' natural tendencies so that we can build more useful products and get more done. Why can't we try to fight bias in the same way?
I'm not sure you're going to establish a moral high ground by explicitly opposing the progress of equality... I understand you have concerns and you may feel you've been wronged by "gender aware" policies/attitudes, but I don't think it's very controversial to say that women are historically disadvantaged and we need to work that out in some way, however that may be.