Americas Greatest stock Opportunity

Source: IBD

Important paper from Google on large batch optimization. They do impressively careful experiments measuring # iterations needed to achieve target validation error at various batch sizes. The main "surprise" is the lack of surprises. [thread]

https://t.co/7QIx5CFdfJ

The paper is a good example of lots of elements of good experimental design. They validate their metric by showing lots of variants give consistent results. They tune hyperparamters separately for each condition, check that optimum isn't at the endpoints, and measure sensitivity.

They have separate experiments where the hold fixed # iterations and # epochs, which (as they explain) measure very different things. They avoid confounds, such as batch norm's artificial dependence between batch size and regularization strength.

When the experiments are done carefully enough, the results are remarkably consistent between different datasets and architectures. Qualitatively, MNIST behaves just like ImageNet.

Importantly, they don't find any evidence for a "sharp/flat optima" effect whereby better optimization leads to worse final results. They have a good discussion of experimental artifacts/confounds in past papers where such effects were reported.

So I was talking to @gewt about Job: A Comedy of Justice and I came up with a theory that I think explains why Heinlein's late-period work is so kinda-terrible and why I still enjoy it so much

So Heinlein had always been very interesting in the short parts of his novels, like the little snippets inside chapters. He had a very fun writing style, and wrote some fun dialogue with fun characters, right?>
It probably comes from how much of his early stuff was short fiction

And I think what happened with a lot of his longer works is that he'd just start writing fun bits and hope it would end up going somewhere or having a bigger plot by the end. like eventually he'd figure out where this was going, then go back and rewrite it into a cohesive whole

and I'm sure he had editors that'd help this process. No editor would let you publish something as rambly and changing-gears-every-other-chapter as The Number Of The Beast, for example... unless you were God-King Of Science Fiction 1980s Robert Heinlein.

so basically I think what happened is that by the 80s (when he was in his seventies!!) he lost the drive to go back and rewrite and he was too Untouchable for editors to make him.

So it turns out that Google Chrome was making everything on my computer slow *even when it wasn’t running*, because it installs something called Keystone which is basically malware.

I made a website because this shouldn’t

Wired first reported on how bad Keystone was 11 years ago when they put it into Google Earth (they seem to put it in all their popular

The fact that Keystone hides itself in Activity Monitor is bizarre. (The only sign of it was excessive CPU usage of WindowServer which is a system process).

I don’t know if Google was doing something nefarious with Keystone, or a third party figured out how to (which Wired warned about). But either way, I’m not inclined to give Google-the-organization the benefit of the doubt (despite the many good people who work on Chrome)...

...since it's been a decade+ and this still hasn't been "fixed".

There is no reason for auto-update software to need to do what Chrome/Keystone was doing. It also has a long history of crashing Macs.