Twitter is, by far, the fastest way to build a high-quality audience.

Why?

It's quicker to write insightful tweets than it is to produce 10min YouTube videos or 1400-word blog posts.

Here's a thread of actionable tactics from studying the fastest-growing Twitter accounts.

The Straddle is my favorite trade these days. But more often than not, one needs to adjust to make a good return from it. There are many ways to do this depending on your view, psychology and imagination. Will discuss a few that I use

The Straddle is a delta neutral strategy and it is important to keep deltas in check during the course of the Trade and not let them run away from you. Of course Volatility is the elephant in the room- but not going there as that will require a separate discussion

The first and most common method is to go 'inverted.' That is to say to shift the untested side to generate additional Premium and increase the runway to Breakeven. So if you start with a Straddle at 700 and price goes to 740, you can move the PE up to say 720.

How much should you move the untested side? While again this is a matter of skill, experience and artistry, the rule of thumb is to cut deltas by half. Remember, prices will move and you have to allow sufficient room for them to fluctuate

The second method is to shift the entire Straddle in the direction of the move. So if you have a 700 Straddle and Price goes to 740, you can shift the Straddle to 720. If you time this right, it can generally be done at virtually no cost or minimal cost.

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.

November is here, and that means a massive shift is coming. And by "massive" I am of course referring to the redefinition of the kilogram unit of mass that the world has been building up to for more than 100 years. Let me explain:

1/ I've had an unhealthy fascination with metrology (the study of measurement) ever since my 2nd year as a physics major when I took a class devoted to duplicating historic physics experiments, so please indulge me for going into heavy detail (get it?) about the kilogram.

2/ So what actually *defines* a unit of measurement? If you're American, you probably know a mile is 5280 feet and a foot is 12 inches and an inch is 2.54 centimeters etc. But where does this chain of definitions end? Is it turtles all the way down?

3/ It's actually not! For all units (even the imperial units used in America) the answers all end with the Système International (SI) unit definitions established and maintained for over 100 years by the Bureau International des Poids et Mesures (BIMP) in France.

4/ At the base of this tower are the SI base units. Just 7 SI base units define every other unit in existence. They are:

Kilogram, kg (mass)
Meter, m (distance)
Second, s (time)
Kelvin, K (temp)
Ampere, A (electric current)
Candela, cd (luminous intensity)
Mole, mol (quantity)

The Haas / Force India argument is fascinating, and the decision of the stewards may still have consequences. The first key finding is that the stewards ruled Racing Point Force India to be a valid constructor. That means that it builds its own cars.

Haas had argued that the cars had been designed by Force India, but as Haas knows only too well, "outsourcing" is legal. The stewards decided that "there is no regulatory support for the argument that Outsourcing of Listed Parts cannot come from a former or excluded team."

In determining this, the stewards also came to the following conclusion: "In relation to the submission by the Racing Point Force India F1 Team that it is not a new team, the Stewards decide that the Racing Point Force India F1 Team is indeed a new team."

This will have a big knock on effect for Haas in its continued arguments over the rights of RPFI as relates to its eligibility and rights under the complex payments structure. Haas has argued all along that RPFI should be treated as a new team and tread the same path that it did.

TLDR? Haas lost the fight but may have won the war. In having its argument that Racing Point hadn't designed their own car thrown out, they gained clarification that RPFI was a new team.