I know I'm sounding ridiculous but #SAIL can do a 4 digit mark in next 3-4 years!!

CMP 120

Krishna and the False Vasudeva
#story

Paundraka Vasudeva was a King mentioned in Bhagavatha Purana. He was friend of Jarasandha, the king of Magadha. He believed that he is Vasudeva Krishna.
Once Paundraka Vasudeva received a letter from Shishupala, stating that he wanted

protection from Krishna, because it was Rukmini's wedding and Shishupala thought Krishna would take away Rukmini.

Paundraka Vasudeva agreed and went to Vidarbha, the Kingdom of Shishupala, but failed to provide protection as Krishna took Rukmini away. Paundraka Vasudeva was

feeling sad. His Minister's cheered him.
They said that Paundraka Vasudeva was the real Vasudeva and Krishna is a cheater. Everyone started to believe this and soon Paundraka Vasudeva soon started to taunt Krishna by saying that Krishna was a cheater.
Paundraka Vasudeva then

challenged Krishna to a war and Krishna said that he would give Paundraka his Chakra and Gadha. Paundraka suspected some foul play and went to King of Kashi for his protection. In battlefield, Krishna came in front of Paundraka, and said that he would throw his Chakra and Gadha

to him. But, Krishna's throw was perfect that the Gadha hurled him to the Ground and the Chakra killed him.
Krishna soon killed king of Kashi with an arrow and his head went flying to Kashi.
Thus Victorious Krishna was recieved by people of Dwaraka.
Hare Krishna 🙏🕉🙏

🌺श्री गरुड़ पुराण - संक्षिप्त वर्णन🌺

हिन्दु धर्म के 18 पुराणों में से एक गरुड़ पुराण का हिन्दु धर्म में बड़ा महत्व है। गरुड़ पुराण में मृत्यु के बाद सद्गती की व्याख्या मिलती है। इस पुराण के अधिष्ठातृ देव भगवान विष्णु हैं, इसलिए ये वैष्णव पुराण है।

गरुड़ पुराण के अनुसार हमारे कर्मों का फल हमें हमारे जीवन-काल में तो मिलता ही है परंतु मृत्यु के बाद भी अच्छे बुरे कार्यों का उनके अनुसार फल मिलता है। इस कारण इस पुराण में निहित ज्ञान को प्राप्त करने के लिए घर के किसी सदस्य की मृत्यु के बाद का समय निर्धारित किया गया है...

..ताकि उस समय हम जीवन-मरण से जुड़े सभी सत्य जान सकें और मृत्यु के कारण बिछडने वाले सदस्य का दुख कम हो सके।
गरुड़ पुराण में विष्णु की भक्ति व अवतारों का विस्तार से उसी प्रकार वर्णन मिलता है जिस प्रकार भगवत पुराण में।आरम्भ में मनु से सृष्टि की उत्पत्ति,ध्रुव चरित्र की कथा मिलती है।

तदुपरांत सुर्य व चंद्र ग्रहों के मंत्र, शिव-पार्वती मंत्र,इन्द्र सम्बंधित मंत्र,सरस्वती मंत्र और नौ शक्तियों के बारे में विस्तार से बताया गया है।
इस पुराण में उन्नीस हज़ार श्लोक बताए जाते हैं और इसे दो भागों में कहा जाता है।
प्रथम भाग में विष्णुभक्ति और पूजा विधियों का उल्लेख है।

मृत्यु के उपरांत गरुड़ पुराण के श्रवण का प्रावधान है ।
पुराण के द्वितीय भाग में 'प्रेतकल्प' का विस्तार से वर्णन और नरकों में जीव के पड़ने का वृत्तांत मिलता है। मरने के बाद मनुष्य की क्या गति होती है, उसका किस प्रकार की योनियों में जन्म होता है, प्रेत योनि से मुक्ति के उपाय...

The Haas / Force India argument is fascinating, and the decision of the stewards may still have consequences. The first key finding is that the stewards ruled Racing Point Force India to be a valid constructor. That means that it builds its own cars.

Haas had argued that the cars had been designed by Force India, but as Haas knows only too well, "outsourcing" is legal. The stewards decided that "there is no regulatory support for the argument that Outsourcing of Listed Parts cannot come from a former or excluded team."

In determining this, the stewards also came to the following conclusion: "In relation to the submission by the Racing Point Force India F1 Team that it is not a new team, the Stewards decide that the Racing Point Force India F1 Team is indeed a new team."

This will have a big knock on effect for Haas in its continued arguments over the rights of RPFI as relates to its eligibility and rights under the complex payments structure. Haas has argued all along that RPFI should be treated as a new team and tread the same path that it did.

TLDR? Haas lost the fight but may have won the war. In having its argument that Racing Point hadn't designed their own car thrown out, they gained clarification that RPFI was a new team.

So there's a class of puzzles called "river crossing puzzles" which involve having to cross a river on a boat/bridge containing some set of individuals/items with restrictions on which ones can be on the boat/left on each shore, right?

and the most common subclass of these problems is the one where you have 3 items/animals to cross with.
This is alternatively called the "fox, goose, and bag of beans" or "wolf, goat, and cabbage" puzzle.

the idea is that your boat can only carry one item at a time, but if you leave the wolf/fox unattended with the goat/goose, the wolf/fox will eat the goat/goose.
and similarly, the goose/goat will eat the beans/cabbage if left alone

so you have to set up a set of actions that never leaves either side of the river in one of the lose-states.

the solution to this variant being:
1. take the goat/goose over
2. return empty
3. take the wolf/fox over
4. return with the goat/goose
5. take the cabbage/beans over
6. return empty
7. take the goat/goose over

1/ The first 18 months of starting a company is often life or death. I must've made 5 different companies that each failed within 9 mo. 😭 Each time the company failed I figured out what I could do better. Eventually startup #6 got to $40K/mo by month 18. Here’s what I learned...

2/ Stay focused! Ignore things that are a waste of time: meetups & conferences, meetings with no clear agenda, fundraising if you're not fundraising, reading lots of tech media articles, etc. Every week should feel like significant progress in the first year.

3/ Your first 5 hires will be the difference between life or death. Choose carefully. Be picky. Many of the things we do at the company still are a result of those early hires' legacy. Have fun as a tight knit team. It will change & evolve as you get bigger so enjoy this moment.

4/ Growth may be flat for the first 9 months. It's gonna be okay. Almost every company has experienced this: Airbnb had to sell cereal in-between, Slack failed as a gaming company first, Tesla sold only 147 cars after 6 years! You probably won't be an overnight success either.

5/ In the beginning, do customer support yourself. You will learn a lot about why your product sucks. I did 5,000+ support tickets when it was the two of us. Delight customers & fix things fast while you learn. It will help you build an amazing intuition about your customers.