(Ie, if you sample the same signal twice for the numbers they did in the study, there’s a 40% chance it’ll be >0.04 away from the original sample, as numeracy was from language)
384 karma · joined March 23, 2025
(Ie, if you sample the same signal twice for the numbers they did in the study, there’s a 40% chance it’ll be >0.04 away from the original sample, as numeracy was from language)
You absolutely should. Tiny sample size and poor statistical method. It is p-hacking plain and simple
Tiny sample size - 36 people completed
Numeracy has R^2 = .27 Language has R^2 = .31
They then run stepwise regression to determine variance contributions, seemingly ignoring their earlier results, and this leads to almost no contribution from numeracy. Why? Because they have ~10% shared variance and stepwise regression is greedy - will just take whatever you give it first.
I can't mention this part enough. If you got a second, very similar language test, and added it to the model, you would _also_ find it has almost no unique variance added.
Every thing they measure is incredibly noisy and they do not once attempt to deal with this. Human based reviewers, time-to-completion, etc.
p-value for "language learning is more significant than numeracy" on the values they give (Steiger test) gives 0.772. Utterly insignificant.
Also, to beat the point home, just think about the argument here: * Numeracy contributes 27% of variance
* Language skills contribute 31% of variance
* After regression step, numeracy contributes only 2% of unique variance. Because you added a correlated variable!
This would put a trader earning $3m/yr as working class. That’s fine I guess, but then we need another distinction, for the difference between that person and a minimum wage worker.
Now in all the conversations where we would say “working class” we use this new term, because we almost always mean things relating to income level rather than labour vs owner.
And so all we’ve done is changed the name for “working class”
It’s a pretty niche use case but it’s deeply frustrating
Not as ergonomic as a direct tree-iterator, but I can't see of an elegant way to introduce that in an imperative language while keeping the forking/recursion aspect clear
I am not a fan of leetcode interviews myself, but I don't think the FAANG process is that bad. I am interested in any specific examples of authors of projects being rejected from big-tech companies for a role where they would work on their own thing
> answer by himself: https://www.quora.com/Whats-the-logic-behind-Google-rejectin...
arith-mean = E[x] , the first moment of x geo-mean = exp(E[log x]) , so log geo-mean = first moment of log x
They are both equivalent in amount of information preserved, but arithmetic preserves additive structure whereas geo preserves multiplicative structure
I agree that we need laws to make "yelling fire and causing stampedes" illegal. I do not agree that "free speech requires an intent to express a point of view" is the correct way of implementing this.
Excellent, now we can ban speech we don’t like by just saying it doesn’t actually express a point of view
I myself have built zsh bindings for helix as that was my main pain point: https://github.com/john-h-k/helix-zsh
My understanding is you can specifically and formally define the natural numbers with addition and multiplication, although multiplication means the language is no longer decidable.
You can define natural numbers with just addition ( Presburger arithmetic ) and it’s decidable.
Im not sure how undecidable <=> “will define things that are similar to natural numbers but are not” but maybe I am missing something
I think there’s lot of dangers and problems with it and frankly I’d probably be happier if it was never invented. But even then I can still see the value it has
atop is (for some reason) touching memory of processes it monitors.
atop is touching this in an insecure way. An executable can cause atop to corrupt its memory.
this has high potential (although not guaranteed) for allowing RCE within atop via a correctly crafted process that atop monitors.
atop is often run in root, and so this otherwise meaningless RCE becomes privilege escalation, which is bad
either this is correct, or cunningham’s law will bring out the correct interpretation
This is… Oddly worded? Unless I’m missing something major (possible), they just mean “writing assembly with microcode in mind”, which is pretty standard for anyone writing optimised assembly, but they’ve written it as if they’re etching new microcode into the CPU