Apollo Hospital👇 https://t.co/3TReZvM53C

Remember: Just because an idea is old doesn't mean it's good.

Knowing whether old ideas are more likely to be good requires understanding whether conditions have changed in important ways.

Horse archery was an amazing method of warfare for over a thousand years...then people invented guns, and suddenly this great idea that had stood the test of time became obsolete.

Then again, when underlying conditions don't change much, tried-and-true approaches are probably better.

"Learning the lessons of history" usually just means assuming ergodicity and stationarity in an informal time-series model...

(end)

1 There's a chasm between an NLP technology that works well in the research lab and something that works for applications that real people use. This was eye-opening when I started my career, and every time I talk to an NLP engineer at @textio, it continues to strike me even now.

2 Research conditions are theoretical and/or idealized. A huge problem for so-called NLP or AI startups with highly credentialed academic founders is that they bring limited knowledge of what it takes to build real products outside the lab.

3 A product is ultimately a thing that people pay for - not just cool technology or user experience. But I’m not even talking about knowledge gaps in go-to-market work. I'm talking purely technical gaps: how you go from science project to performant + delightful user experience.

4 Most commoditized NLP packages solve well-understood problems in standard ways that sacrifice either precision or performance. In a research lab, this is not usually a hard trade-off; in general, no one is using what you make, so performance is less important than precision.

5 In software, when you’re making something for real people to use, these tradeoffs are a big deal. Especially if you’re asking those people to pay for what you’ve made (can’t get away from that pesky GTM thinking). They expect quality, which includes precision AND performance.

SRI MOOKAMBIKA DEVI, KOLLUR (KAR)

There was an Asura, Kaumasura, who was doing penance to please Shiva and get a boon. To prevent him from asking for a boon, Devi Saraswati made him dumb (hence called Mookasur)
Later, Adi Parashakti slayed him and came to be called Mookambika.

It is said that Adi Shankaracharya had a vision in which Devi agreed to follow him provided he did not look back. He kept walking and was assured of her presence due to the sound of anklets. When he reached here in Kollur, he turned back as the sound of anklets had stopped.

So Devi stayed here and merged with the lingam. The place came to be called Mookambika Kshetram.
The linga has integrated on it’s left side MahaKali, Maha Lakshmi and Maha Saraswathi and on the right side- Brahma, Vishnu and Shiva.

A swarna rekha (gold line) divides this linga into left and right portion. Adi Shakthi in this Udhbhavlinga form appears only here.
Devi sits in padmasana and has 4 hands.
Adi Shankaracharya installed the Sri Chakra in front of Devi and also composed the Soundarya Lahiri here.

🎉🎉 PHP 7.3 is here!

Here are the things I'm excited about.

🚂 Trailing commas in function/method calls!

This will certainly be a required styling choice for me. Same delightful benefits of trailing comma in multi-line PHP arrays, and JavaScript objects.

🧵 Less disgusting heredoc syntax!

Inlining heredoc strings in any way right now is grrrosssss. Now we get sensible capabilities. Everything that was wrong with it is now fixed!

(Ignore the bad syntax highlighting)

☠️ Finally, not-so-silent json_decode error detection!

This really sucked before, now it just sucks a bit less (who wants to pass a 4th param and pass 2 default params first? (helper function anybody?)

📜 Not horrible functions for getting the first and last item (or key) from an array!

Before you either strung a bunch of functions together or messed with internal array pointers. This is a much-needed improvement.