How I Became a 6-Figure Solopreneur

In this thread, I'll briefly explain:

1. The steps I took
2. How I kept my costs low
3. How you might be able to do the same

Keep reading…

👇 Thread. New deck getting published this week: "Consumer startups are awesome, and here's what I'm looking to invest in at Andreessen Horowitz." If you want to read it, subscribe to my newsletter here: https://t.co/262t8eh0wf

1/ A lot of new consumer technologies have been introduced to US households in the last 100 years. But it's taken many of them - like the telephone - more than 50 years to get to the majority of the US. Why is that?

2/ We had to literally teach people how to use phone. Which end goes to your mouth, which goes to your ear. Say "hello" when people call. The motivation of consumers to talk to their friends has always been there, but we had to teach the behavior

3/ If you compare phones to the latest technologies, there's been a huge shift. Things are being picked up much faster.

4/ Even while there's been all this innovation recently, physically speaking, we are still the same human beings from 100,000 years ago.

Stories of Guruvayurappan
Shri Krishna Leela

This is a beautiful story of Guruvayurappan. Once there lived in Guruvayur a poor family. Kitta, his wife & kids were struggling for their daily needs. With only a coconut tree in house, he earned a living by selling coconuts.

Kitta was from a low caste family. He was a great devotee of Guruvayurappan. Everyday before going to work he always prayed infront of a picture of Guruvayurappan in his house. His only wish was to worship at Guruvayur & have annadanam in temple. But he was not allowed there

It was Utsavam time in Guruvayur. From far behind kitta and family worshipped Guruvayurappan. Annadanam was given daily and no one was left empty stomach. Only Kitta didn't receive. That night, it was only Kitta's family who was sleeping without food. After temple nada closed

Shri Krishna, dressed himself as a Brahmin went to temple Kitchen. He packed food and went directly to kitta's house. Reaching Kitta's house, Shri Krishna told he was sent by a cook of Guruvayur temple and gave them the food he packed. Kitta and family was very happy seeing food.

When Kitta finished his food, Brahmin asked it will be better if he get a tender coconut( karikku)to drink. Kitta climbed the tree and gave all coconuts to him. After having 1 tender coconut, the Brahmin asked to bring remaining coconuts to Guruvayur temple the next day.

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.

So it turns out that Google Chrome was making everything on my computer slow *even when it wasn’t running*, because it installs something called Keystone which is basically malware.

I made a website because this shouldn’t

Wired first reported on how bad Keystone was 11 years ago when they put it into Google Earth (they seem to put it in all their popular

The fact that Keystone hides itself in Activity Monitor is bizarre. (The only sign of it was excessive CPU usage of WindowServer which is a system process).

I don’t know if Google was doing something nefarious with Keystone, or a third party figured out how to (which Wired warned about). But either way, I’m not inclined to give Google-the-organization the benefit of the doubt (despite the many good people who work on Chrome)...

...since it's been a decade+ and this still hasn't been "fixed".

There is no reason for auto-update software to need to do what Chrome/Keystone was doing. It also has a long history of crashing Macs.