To add some color to this, the culture for a very long time would reward folks that came up with novel solutions to problems or novel products. These folks would dedicate some effort into the implementation, land the thing, then secure a promo with no regard for the sustainability of the aforementioned solution. Once landed, attention goes elsewhere and the thing is left to languish.
This behavior has been observed publicly in the Kubernetes space where Google has contributed substantially.
> Ah. So what we have here is, regardless of whether you agree it's true or not, a political agenda masquerading as a personality test. It's purpose is to argue Peterson's vocal political belief that the gender pay gap is not an issue, because women are biologically better at being nurses instead of engineers. His proof? Just look at those Scandinavians, they have completely solved sexism (citation needed) and still see this gap
I'm not sure it's a political belief per se so much as a refutation of the implicit assumption that the gender pay gap is entirely the result of sexism and more likely the result of other factors, not least of which are the traits and proclivities of either sex.
I'm not prepared to debate whether or not his argument on the topic is legitimate, but it is something that he has elaborated on and supported with some data.
The H10 is the gold standard for HRMs and the one most commonly used by anyone doing experimentation with HRV. I don't have the specs memorized off hand, by my recollection is that it does a better job of capturing the entire waveform.
> you can only compare performance across a cohort
I can't accept this premise. Optimally the persons responsible for managing engineering staff should be able to independently determine whether the work being produced was of sufficient quality or not regardless of the cohort.
At issue here, I believe is that this is a difficult thing to cultivate consistently in many corporations and so there's some desire to create standardized metrics for performance against which a cohort is measured. Regardless, most large tech firms have some kind of well defined rubric against which the engineers are measured.
To say nothing of the ethics of cheating, I think this behavior speaks to the value of the interview process. If it can be gamed so easily, it's likely not a great measure of the quality of the candidate and the companies that have implemented deserve the hires they make.
It'd doubtful the folks at the company actually mind that the interviews are being cheated. If the candidates appear to be qualified and appear to be fill the role for which they were hired and appear to be competent in that role, that's sufficient for most corporations and one of the problems working in "tech". That is to say, there are plenty of people in it that appear to be doing a thing, but aren't actually capable.
Somewhere in this thread a poster mentioned woodworking, which is a nice contrast. If you hire a carpenter, it becomes obvious pretty quickly if the carpenter is competent.
I love it, but when it fails at scale, it can be hard to reason about. Or at least that was the case when I was using it a few years back. Still keen to try it again and see what's changed. I haven't run it since bluestore was released.
How does interacting with reps have anything to do with "onboarding"? This is more or less an evaluation of how easy it is to take advantage of credits.
I'd be more interested in how easy it is to use a credit card and get a service off the ground. What is the relative quality of the products on offer by either vendor?
Yes, that's a small amount of data. I've worked at small companies with an order of magnitude more data per day and larger companies with three orders of magnitude more data per day flowing into a text indexing service.
Again, very minor use case. Not worth expending effort on. I attempted to convince the lawyers that we should just yolo it because the product had no actual revenue.
And a whole thread on HN about it:
https://news.ycombinator.com/item?id=30938842