If you post something to twitter, a social media platform by which ideas are shared, and you don't want people to comment on it or provide their opinions, you can use many tools on twitter (locking account, changing who can reply).

Calling disagreement "disrespectful" is bizarre

क्या आप जानते हैं कि क्या है, पितृ पक्ष में कौवे को खाना देने के पीछे का वैज्ञानिक कारण!

श्राद्ध पक्ष में कौओं का बड़ा ही महत्व है। कहते है कौआ यम का प्रतीक है, यदि आपके हाथों दिया गया भोजन ग्रहण कर ले, तो ऐसा माना जाता है कि पितरों की कृपा आपके ऊपर है और वे आपसे ख़ुश है।

कुछ लोग कहते हैं की व्यक्ति मरकर सबसे पहले कौवे के रूप में जन्म लेता है और उसे खाना खिलाने से वह भोजन पितरों को मिलता है

शायद हम सबने अपने घर के किसी बड़े बुज़ुर्ग, किसी पंडित या ज्योतिषाचार्य से ये सुना होगा। वे अनगिनत किस्से सुनाएंगे, कहेंगे बड़े बुज़ुर्ग कह गए इसीलिए ऐसा करना

शायद ही हमें कोई इसके पीछे का वैज्ञानिक कारण बता सके।

हमारे ऋषि मुनि और पौराणिक काल में रहने वाले लोग मुर्ख नहीं थे! कभी सोचियेगा कौवों को पितृ पक्ष में खिलाई खीर हमारे पूर्वजों तक कैसे पहुंचेगी?

हमारे ऋषि मुनि विद्वान थे, वे जो बात करते या कहते थे उसके पीछे कोई न कोई वैज्ञानिक कारण छुपा होता था।

एक बहुत रोचक तथ्य है पितृ पक्ष, भादो( भाद्रपद) प्रकृति और काक के बीच।

एक बात जो कह सकते कि हम सब ने स्वतः उग आये पीपल या बरगद का पेड़/ पौधा किसी न किसी दीवार, पुरानी

इमारत, पर्वत या अट्टालिकाओं पर ज़रूर देखा होगा। देखा है न?

ज़रा सोचिये पीपल या बरगद की बीज कैसे पहुंचे होंगे वहाँ तक? इनके बीज इतने हल्के भी नहीं होते के हवा उन्हें उड़ाके ले जा सके।

So, I want to talk about how sexual harassment and fair pay are linked at Google (and beyond), because I think that's an angle that isn't being highlighted enough in the coverage of these walk-outs. I'm going to frame it largely around my personal experience there. Thread.

When I was sexually harassed by the director of the area I was working in, I was afraid to report it because I was worried that "getting him in trouble" would result in the subtle retaliation of missed leadership opportunities.

I wanted to continue working on the team I was on, because I'd gained a lot of very deep knowledge and expertise in that area, as well as reputation and camaraderie with the other folks working in that area. I didn't want to make the situation more "difficult."

To get promoted at Google, several need to happen: 1. you need opportunities for ownership and leadership above your current level (basically, opportunities to show you're working at the next level you're trying to get promoted to). The work you're "assigned" has a big impact.

2. You need glowing reviews from peers, *at or particularly above the level you're hoping to get promoted to.* Basically, you need people a lot more senior than you to say you're doing awesome work.

🚢 Atomic Essays Republishing Framework 🚢

1. Write Atomic Essay
2. Post image on Twitter
3. (Bonus) Copy/paste text as thread
4. Find relevant Question on Quora. Copy/paste Atomic Essay + image.
5. Copy/paste again on Medium.
6. Again on LinkedIn
7. Win

Guide below ✍️🚢👇

Step 1: Write Atomic Essay

I really enjoy writing right inside the Figma template. It helps give me a good sense of exactly how much "real estate" I have/have left before my time us up and I'm out of space.

Once finished, I export the image and send to my phone on Slack.

Step 2: Post image on Twitter

Before I publish my Atomic Essay on Twitter, I use the Edit/Photo Markup function on the iPhone to highlight standout sentences.

These are usually power-phrases: things the reader skims and thinks, "That's interesting," prompting them to read more.

Step 3: For the Ship 30 for 30 challenge, I only turn Atomic Essays into threads if...

1. The piece is SUPER actionable and lends itself well to the thread format (lots of bullets, quick points, lists, etc.)

or...

2. I'm referencing research and want to link to the pieces.

Step 4: Find relevant Question on Quora. Copy/paste Atomic Essay + image.

Search on Quora around the topic you wrote about. Find a related Question. Copy/paste the whole Atomic Essay as your "answer" (& fix formatting). Then include image so it appears in the thumbnail.

In 1937, a trucker got frustrated waiting for his cargo to be unloaded. He later sold his company for $1.1 billion.

Here’s the story of how Malcom McLean made a billion dollars and which startup could be following in his footsteps. (Inspired by our episode with @laurabehrenswu)

In the early 1950s, the shipping industry was a dying business.

New York’s docks were handling half as much domestic cargo in the early 1950s as they had been in the depressed 1930s.

In thirty years, no one had invested significant money in coastal shipping.

Why?

As McLean found out, loading ships was difficult and slow.

A truck or train would deliver items to the port. Each item was unloaded separately, recorded, and carried to storage.

When a ship was ready, each item was taken from storage, counted again, and hauled on-board.

The cost of this labor was significant. As one expert at the time explained:

“A four-thousand-mile voyage for a shipment might consume 50 percent of its costs in covering just the two ten-mile movements through two ports.”

Yet, despite the industry’s issues, it felt little pressure to change.

Foreigners were barred from operating domestically. Cartels ran international routes. And gov. subsidies eased the pain of labor costs.

Reshaping the industry needed an outsider.

Enter Malcolm McLean.

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.