[Thread]
For those who followed last summer's exposure of #GenevanCommons hate group, there is an update.

It seems beneath my dignity to report it.
But then again, so much of what women end up having to say is beneath our dignity. 1/11

@cain_nate My friend Nate Cain and I have worked hundreds of hours with various politicians and legal groups trying to explain the election laws and how they fit together. There are many misperceptions of what happened during this election and what it means.

Simply put, our election laws are an intricate tapestry designed to ensure accuracy and prevent fraud. They work together like parts of a car. But when certain parts fail, the car is just a hunk of scrap iron and plastic. In this case critical parts failed.
2/

You do not have to prove fraud or intent, you just have to show that the election officials were unable to conduct an election that met the law and relevant certification requirements. In this case, the election does not come close to meeting accuracy requirements.
3/

These specifications are found deep in laws like FISMA, HAVA, and state adoptions of EAC guidance. 1 ballot error out of 125,000 or 1 position read error out of 500,000. Just look at the discrepancies between incoming ballot counts and total votes, the system fails.
4/

It is worse in the the swing states in Democrat strongholds but it is bad in many places. You add the apparent losses of ballots through the Mail and error rates in the ‘system’ are staggering. Why do we have these rules? Sure it is to prevent fraud, but......
5/

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.

#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

I am done giving this doctor or team grace. I started with "We are tremendously grateful for all you are doing." He seemed irritated to speak to us. Literally I asked, "What is the likelihood our mom will die on current support, in the next 24 hours, so we can plan travel?"

He hammered us with how severe this was and that was. Yes, that is why I am asking the question. "We are asking you to be a thought partner so we can make responsible decisions as the family." I had had pre-conversations with doctor friends to understand the numbers and prognosis

He said "It would be illegal for me to tell you that she won't die, then she dies." Yes, that is why I said LIKELIHOOD - critical care docs deal in likelihoods. It so frustrating to be on this side and not get a fraction of the standard that I have been held to and hold myself to

Then I made the error of saying, "I'm a pediatrician, I literally do this work on family-centered, compassionate care." to which the charge nurse answered, "It is not the work we do. We keep people alive." End of life care IS your job. Planning IS your job. It's not just numbers

Compassion is not only a pediatric thing while critical care/end of life can proudly lack it. I've had more end of life conversations than I want to remember. My mom is not numbers. She is a human being. I am modulating my voice, complimenting you, leveraging my network.