Loading comment...
Loading parent story...
Loading comment...
The best predictors of job performance are a simulation of the job and past performance. This is not new research or a secret.
The reason I'm not living the dream could be that it's impossible, or I haven't tried hard enough. I don't want to believe either of those. I'd rather believe that something happened to me in my past that rewired my brain to stifle my full potential. Then I could still hope to someday achieve my dreams, while not doing anything to progress towards them.
It's not popular because it's right. It's popular because it's so, so appealing.
IDK, I think there are obvious low-hanging attempts [0] such as: do not display secret codes in stable position on screen? Hide it when in background? Move it around to make timing attacks difficult? Change colours and contrast (over time)? Static noise around? Do not show it whole at the time (not necessarily so that user could observe it: just blink parts of it in and out maybe)? Admittedly, all of this will harm UX more or less, but in naïve theory should significantly raise demands for the attacker.
[0] Provided the target of the secret stealing is not in fact some system static raster snapshot containing the secret, cached for task switcher or something like that.
So much falls out of that reframing.
Then it's fine-tuned on: situation + intent => action => result
So much falls out of that reframing.
Loading parent story...
Loading comment...
Loading parent story...
Loading comment...
Consider repeatedly looping through n+1 objects when only n fit in cache. In that case LRU misses/evicts on every lookup! Your cache is useless and performance falls of a cliff! 2-random turns that performance cliff into a gentle slope with a long tail(?)
I bet this effect happens when people try to be smart and loop through n items, but have too much additional data to fit in registers.
There exists a problem in real life that you can solve in the simple case, and invoke a theorem in the general case.
Sure, it's unintuitive that I shouldn't go all in on the smallest variance choice. That's a great start. But, learning the formula and a proof doesn't update that bad intuition. How can I get a generalizable feel for these types of problems? Is there a more satisfying "why" than "because the math works out"? Does anyone else find it much easier to criticize others than themselves and wants to proofread my next blog post?