I heard about people talking behind my back:

It reminded me of a quote from Dale Carnegie:

1/ Someone emailed me asking how to break into VC, so I wanted to answer on Twitter where others could see and contribute to the conversation.

2/ “Being a VC” can mean a lot of different things, so it’s worth asking:

What actual activities do you want to do?

- Deep market analysis?
- Be in the flow of information and people?
- Make deals?
- Work closely w/ founders over time (e.g take board seats?)
- Manage capital?

3/ It’s worth specifying what type of VC you might like to become — as there are different archetypes. E.g.

- Benchmark (Lead series A/B - couple investments a year)
- First Round (Lead seed rounds, partner w/ a few companies a year)
- SV Angel (Make lots of seed investments)

4/ Continued:

Expa - Incubate companies

YC / Village Global - Build a platform to help entrepreneurs at scale

Do you want to join a firm or start one? There’s a lot to consider.

Different paths will require different skillsets & sets of experiences.

5/ Since the person who wrote the email is a young person trying to break into VC by joining a firm (and who doesn’t want to start a company), I’ll tailor this tweet storm to that goal. There’s some overlap.

1) Core attributes of a promising founder worth following:
- Progress/trajectory over time
- How well they lead a team &
- Make the vision happen
- Most impressed when someone is way ahead of where you thought they would be when you check up/see them a few months later.

2) Indie Makers have such a benefit of being small, fast, nimble workers in comparison to big companies.

We can easily pivot and vastly change a project of ours. We can change as we learn more about our users.

Big companies can take months/years for even the smallest of pivots.

3) Before you find a product market you can pivot your project as many times as necessary until you find something that works.

Then you only have one thing to do: scale, scale, scale.

4) Be obsessed with the little details.
- listen to every single person who uses your product
- reply to every single person who emails you about your product
- ask them what they like and do not like
- iterate your product, make changes, pivot if necessary

5) Paul Graham's (@paulg) name came up with a feeling of great admiration! Naturally! It was Paul who said:

In the early stages of a company just;
- write code
- talk/sell to customers to stress test your idea

Nothing else.

Surkanda devi mandir is a famous shrine of Hindus located near Kaddukhal distt of Uttarakhand, 11 Km from the town of Dhanaulti and 35 Km from Mussoorie.
The Temple is one of the 51 Shakti Peethas spread all over Indian Subcontinent and is dedicated to Goddess Surkanda.

Nestled on a Hill at an Altitude of 2700 m approx, the place offers a splendid view of the snow capped mountains, the picturesque scenic beauty that offers an experience of the lifetime.
The Temple build in the traditional Garhwal style exuberates the Architectural splendour.

The origins of the Surkanda Mata Mandir is attributed to Goddess Sati, consort of Bhagwan Shiv who in a rage immolated herself in her arrogant Father Daksha's Yajna Kund bcoz he didn't invite Bhagwan Shiv in the Yajna.

Devastated by the death of Sati Shiva wandered all over the cosmos performing Tandava-The Dance of Cosmic Destruction.Fearing the total annihilation of cosmos, Gods requested Bhagwan Vishnu to pacify Shiva.Bhagwan Vishnu then used his discuss to destroy the burning corps of Sati.

The pieces of Sati Mata's body then got scattered all over the region which were later established as Shakti Peethas by Bhagwan Shiva himself.Its believed that the head of Sati fell here and it was called Sirkhanda Mata Temple before, but with passage of time it became Surkanda.

The 2018 State of JavaScript survey is out. They got 20,000 responses and have some delicious, delicious data. I'mma thread in some highlights:

First up: JavaScript flavors. There's TypeScript at 47% adoption, a tad higher than npm's own survey results (which said 46%). npm's survey is coming up again soon and will ask about TypeScript in a lot more detail.

I really, *really* like SoJ's "would not use again" question, which lets people who've abandoned a tech self-identify. This is noticeable in the graph above with Flow users -- 41% of people who've used Flow say they wouldn't use it again.

Now JavaScript frameworks. It's been a full year since npm's survey, so these numbers differ from ours in the directions I expected:
React 65% (vs. 60%)
Vue 29% (vs. 24%)
Ember 5% (vs 4%, I was expecting a bigger rise)

But there's a shocker in here: Angular.

npm's survey had Angular at 40% last year and SoJ has it at either:
- 58% (if you include those who don't want to use it again)
- 24% (if you count only those who like it)
Since npm's question didn't ask if they intend to *continue* using it I think that might explain this.