Why believing in fortune telling, tarot cards, and zodiac signs is major shirk 🧵

#Suven – Journey of my first 50 bagger…

I bought #Suven first in Apr 2013 around Rs 20…today after almost 7.5 years, its Rs 1000 (Suven pharma 920 adjusted for bonus + Suven Life 80)..CAGR of almost 68% for 7.5 years. I am fortunate to hold it throughout the journey and

1/n

add on multiple occasions on way up. Like to share my experience in this thread for everyone’s benefit..

First time I bought because I like the management focus on R&D. It had chosen the most difficult therapeutic area in pharma which is CNS and it was investing the cash

2/n

flow it used to earn from CRAMS. It also used to write off all the R&D expenses in the P&L instead of capitalizing it in BS. That gave me lot of comfort about management quality.

I kept on adding as funds keep coming. I remember giving a public presentation on Suven in

3/n

Mumbai at one analyst meet in Nov 2017 when it was trading at Rs 160. There was a huge call option embedded at that time in the form of SUVN-502. That would have been the blockbuster molecule if succeeded with market potential of $10 Bn plus..result was due in Dec 2019,

4/n

I loaded around 250-300 knowing the value of CRAMS business itself is more than 300.

SUVN-502 failed in phase-II trials, stock was down 15% from 300 to 250 in a single day, I added heavily. it was largest allocation in my portfolio because I knew the value of CRAMS business

5/n

So, here's my contrarian take on Why Trunk-Based Development Is Great But Probably Won't Work For You. Buckle up, it's a long one.

From time to time I talk about, or boost someone else's discussion of, "classical" continuous integration/trunk-based development/push-to-master/whatever. I do this because I've personally worked like this and I genuinely think it's a marvelous way to write software.

I've also, at this point in my career, failed—a bunch of times!—to bring this technique into practical use on the teams and organizations I've worked with. As a result, while I still do it myself, I don't focus as much on encouraging it in others.

The technoculture that's presently in vogue is what I think of as async/individual—optimize for the individual, performance-manage the individual, decouple the individual from others so they can be their best, most productive, most heroic selves.

This is in contrast to what I think of as sync/team—a culture that leans into interdependence and collaboration. If you've never worked on a team that collaborates very closely every day for months or years on end (and likes it) you've likely not experienced a team like this.