I’ve been using a mixture of email providers, like Protonmail for example. I was wondering if that’s about as good as it gets in terms of security.

The only universal job description of a CEO is to make sure the company wins. You can do this as the founder even if you have a lot of flaws that would normally disqualify you as a CEO as long as you hire people that complement your own skills and let them do their jobs. That experienced CEO with a fancy MBA may not have the skill gaps you have, but he or she won’t understand the users as well, won’t have the same product instincts, and won’t care as much.

--

The prime directive of great execution is “Never lose momentum”. But how do you do it?

The most important way is to make it your top priority. The company does what the CEO measures. It’s valuable to have a single metric that the company optimizes, and it’s worth time to figure out the right growth metric. If you care about growth, and you set the execution bar, the rest of the company will focus on it.

--

Earlier I mentioned that the only universal job description of the CEO is to make sure the company wins. Although that’s true, I wanted to talk a little more specifically about how a CEO should spend his or her time.

A CEO has to 1) set the vision and strategy for the company, 2) evangelize the company to everyone, 3) hire and manage the team, especially in areas where you yourself have gaps 4) raise money, and 5) set the execution quality bar.

In addition to these, find whatever parts of the business you love the most, and stay engaged there.

--

I think if you nail those parts, it probably doesn't matter how hard you work. Paul Buchheit observes that the world rewards results, not hard work.

That's done on purpose to discourage people from posting (or reading) them too often. PG was afraid letting people write text posts would lead to "blogging."

There was never any real chance of this forum going mainstream, not because it was too ugly and awkward but because it didn't have any mainstream appeal. Negative reinforcements like making the text purposely difficult to read mostly just punish existing users.

Still, I can't seem to be able to collapse thread branches because it requires javascript. That's a shame.

I wonder if w3m would recognize something like:

    .collapse:checked + .content-and-replies-container {
      display: none;
    }

Not really. You have to pay the ransom^W^W$100 for a developer account every year.

Matasano used to mail it to all their potential candidates and told them to read chapters N throgh M.

Unfortunately I've forgotten the values of N and M, so just read the whole thing. It's worth the time.

You probably won’t get a 2x boost from it. But you might notice some improvements. It’s worth trying if you can test it quickly.

Software best practices are like flossing: good in the long term, but probably not crucial to keeping your bite.