How to get the best image performance (Updated 2021)

1️⃣ Use `width` and `height` to prevent layout shift
2️⃣ Lazy-load images as they enter the viewport
3️⃣ Use modern image formats (WebP, AVIF)
4️⃣ Serve correctly sized images using `srcset`
5️⃣ Provide blur-up placeholders

THREAD ON IRONFLY

These days the most preferred strategy for option sellers due to improved margins is IRONFLY. It's essentially a short straddle with long strangle. Long strangle acting as 'WINGS', which help in capping the unlimited risk associated with a short straddle.(1/n)

You can also view the position as a combination of Cal & Put credit spreads, if that makes it more easy for you.

There are 3 important things to understand while trading this strategy:

1) Initial size of the Wings
2) Risk Management
3) Adjustments

(2/n)

Since we are selling an ATM straddle, the 1st question is how far our wings should be? Ideally i sell .50 delta straddle & buy .20 or .10 OTM strangle, depending on my view on volatility. So the distance of wings depends on the IV setup. Higher the IVs, greater the distance.(3/n)

If you don't understand greeks, then ideally with 30 days to expiry (dte), wings should be around 300pts either side. If your trading in weekly then it should be not more than 200pts. Higher the premiums, higher the distance as we have more cushion of theta. (4/n)

It is important to understand that we need to reduce the distance of wings with time so as to manage our RISK in gap openings or sudden volatile move. So for eg. if you started with 300pt wings with 30dte, the wings wouldn't give the same protection when there is 7dte. (5/n)

Thread Pt 3 Who is Prometheus?

1. In Greek mythology, Prometheus, is a Titan of fire. Prometheus is a culture hero & trickster figure who is credited with the creation of humanity from clay, and who defies the gods by stealing fire and giving it to humanity as civilization.

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.