Hey all you ‘nothing is habbening’ guys 👋.

Check this out

This was last night in Sterling Virginia

SRI LALITHAMBIGAI, THIRUMEYACHUR (TN)
#bharatmandir #navratri2021

Kshetram where Shiva is worshipped as Meghanatha and his consort is Lalithambigai seen in Abhay mudra.
Once, a demon Pandasura was harassing the Devas who went to Devi Parashakti for protection. 
@GunduHuDuGa

Devi rose from a Yaga Gunda, mounted on the Sri Chakra Rath with the name Lalithambika, waged a war against Pandasura and destroyed him.  When her fury did not subside, Shiva asked her to go to Earth, assume the name Manonmani, perform penance and shed her fury.

Shiva blessed Devi to be Shanta nayagi. There is a sculpture here depicting Shiva pacifying Devi. If you observe closely, you can see that from your left hand side there will be a smile on Her face and if you see from your right hand side you can see anger in Her face.

Hayagriva taught the greatness of Lalitha Sahasranama to Rishi Agasthya. Pleased with his devotion, Ma Lalithambikai appeared before Agastya. He is believed to have then sung Lalita Navaratnamala in praise of Devi. He has also composed a hymn named Rahasyanamasahasram.

SRISAILAM: KASHI OF THE SOUTH (AP)
#andhratemples

The divine abode of Mallikarjuna Swamy (Jyotirlinga) and Devi Brahmaramba (Shaktipeeth).

When Ganesha was married before Kartikeya, he left in anger to Kraunch mountain. Shiva and Parvati also followed him there.

Shiva assumed the form of Jyotirlinga and resided on the mountain by the name of Mallikarjuna. Mallika means Parvati while Arjuna is another name of Shiva
It is also said that once, a princess Chandravathi, saw a cow shedding milk on a rock resembling a shivlingam.
@DubeyYash1911

She started praying to the lingam daily and used to offer jasmine (mallika pushpam) daily. Pleased Shiva appeared before her and agreed to wear jasmine garland (mallika pushpmala) on his head permanently. Since then, Shiva became known as Mallikarjun Swamy.

At this place, Shakti took the form of Bhramaram (bee) to kill Arunasur and settled as Bhramaramba Devi. The place is a Shakti Peeth as the neck portion of Devi Sati fell here.

It is said that by merely seeing the hill, one is emancipated from all his sins and worries.

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.

The 2018 State of JavaScript survey is out. They got 20,000 responses and have some delicious, delicious data. I'mma thread in some highlights:

First up: JavaScript flavors. There's TypeScript at 47% adoption, a tad higher than npm's own survey results (which said 46%). npm's survey is coming up again soon and will ask about TypeScript in a lot more detail.

I really, *really* like SoJ's "would not use again" question, which lets people who've abandoned a tech self-identify. This is noticeable in the graph above with Flow users -- 41% of people who've used Flow say they wouldn't use it again.

Now JavaScript frameworks. It's been a full year since npm's survey, so these numbers differ from ours in the directions I expected:
React 65% (vs. 60%)
Vue 29% (vs. 24%)
Ember 5% (vs 4%, I was expecting a bigger rise)

But there's a shocker in here: Angular.

npm's survey had Angular at 40% last year and SoJ has it at either:
- 58% (if you include those who don't want to use it again)
- 24% (if you count only those who like it)
Since npm's question didn't ask if they intend to *continue* using it I think that might explain this.