Jubilant Ingrevia - Key learning?

It is important to analyse the strength of the breakout. If the price does not continues the move in 1 or 2 sessions and candles show long upper wicks, it is better to bring the SL closer. Distribution sign.

Will be helpful in next breakouts. https://t.co/AtZOj4bKeT

The man who invented autocorrect should burn in hello.

It was meant to put a smile on your face. Please stop sending me instructions on how to turn my autocorrect off. 😳🤔

Texted my friends to ask if I could take their kids with me to Satan... still have not heard back from them. I meant Santa...

Thanks for all the love, I appreciate a follow. 💗

STORY OF PURANAS AND SUB PURANA (उप पुराण).

We have already gone through the series on importance & characteristics of all the eighteen Purans. We also know that originally there were hundred crore shlokas but were divided by Vyas in each Kalp and was compiled as eighteen Purans

for the common people to understand it properly and now their total is about four lakhs.

In Brahm Puran, Brahma preached this to Marichi. So this Puran of ten thousand shlokas is called Brahm Puran.

In Padma Puran, the base of the story is the appearance of Brahma on a lotus(Padm) from Vishnu' s navel.This has fifty five thousand shlokas.

Vishnu Puran is primarily based in Varah kalp. This book is on Vishnu and this book has twenty three thousand shlokas.

Vaayu Puran is written in Shwet Kalp and has twenty four thousand shlokas. Here Vayudev preaches about Dharma.

In Bhagwat Puran, which is written with the base of Gayatri mantra describes Dharma extensively. It has 18000 shlokas. It also mentions the story of Vritrasur.

In Narad Puran, which has twenty five thousand shlokas, is a sermon on Dharma by Narad based in Brihad Kalp.

Markandeya Puran has nine thousand shlokas and here it is through the birds that Dharma is described.

#SatiSavitri #RealLifeExperiences #BharatDarshana

Bharat Darshana publishes a small monthly magazine which has some very interesting puranic anecdotes and snippets.

When I picked up this month's magazine, I was intrigued by a story which I want to share as below

1/

This is a real-life incident as narrated by Prof. Krishna Bihari Pandey titled "Sati Savitri"

Sati Savitri is a well known puranic figure from Srimad DeviBhagwatham and Mahabharatha as one of those who fought with Yama to save her husband.

2/

This story is a modern real-life experience which mimics the puranic account in it's own unique way.

The story occurs in 1975 with Prof and his wife in Delhi with professor working as a researcher in university. Prof's family is in Allahabad in a large joint family

3/

Once Prof gets to know that his mother is not keeping well. He goes to his native and brings his mother. With dedicated care of his wife, his mother recovers quite remarkably and regains full stamina and strength

Mother-in-law & Daughter-in-law go out for shopping frequently

4/

Life's going smooth until one day when they receive a telegram that Prof's father is not keeping well.

His mother is distressed about the situation and requests her son to take her to the native. Prof is a little angry due to frequent travels and turns it down

5/

🎉🎉 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.

A thread on HN about bad code in legacy projects both makes me think how little we've learned as a discipline over the years and, honestly, how little credit we give ourselves for some pretty major

Fun going down this list and thinking: "Hmm, plausible at a well-run modern software shop", "Hmm, possible, but requires implausible tradeoffs", "Literally disallowed by languages", and "If you were to attempt doing that our test suite wouldn't let you merge."

I think we as an industry celebrate (not quite the right word) failure too much and don't celebrate success nearly enough. There is no DailyWTF for competent execution, word of which generally stays pretty local to the source while incompetence passes into legend.

Alrighty let me try to thread the needle on being the change I want to see in the world while not giving away anything that will get me in trouble:

Ruby has wonderful developer ergonomics. Typed languages are easier for machines to guarantee the correctness of. We built a type checker for Ruby (and I believe it is slated for OSS release sometime).

c.f.