Why we sold only CE's today ?

A small 🧵

Collaborated with @AdityaTodmal

• BNF reversed from 32155 (low made on Mar'8)

• One side rally to butcher the CE writers

• Gap up opening by ~1300 points

• From Mar'8 low till today open ~2800 point rally

• 2800 point rally in just 1.5days

• Trend on the larger TF still bearish
• Due to election results we decided no to carry any overnight positions

• Selling PE on the back of 2800 point rally would have been disastrous due to unfavorable R/R

• So we were very clear to short only CE's

• But then need to follow the trend
• We decided to short CE at the break of first 5min candle

• By 9.45 it started to reverse
• Spotted M pattern at the resistance and started shorting CE's thereafter i.e. post 12.12 hours
• Also BNF resisted at the weekly Channel BD re-test zone
• Patterns Made in BNF:

1. W pattern near lows, made on March 8,
(near 32115 lows, which is also the 1st demand zone in weekly)
https://t.co/YGMfQ6TVQt
2. Flag pattern post the BO of W pattern

https://t.co/SqLs3Ve2nU
3. M pattern near the upper levels on March 10
• Hope this helped to understand the logic for shorting only CE's in today's expiry

• If you found this useful, please do RT first tweet

See past 🧵 here:

@AdityaTodmal
&
@niki_poojary

More from Nikita Poojary

Over the past month, we have shared 15 powerful threads:

These threads cover topics like:
• Trading
• Psychology
• Strategies (both directional & non-directional)
• Investing
• Free tools for traders
• Free technical analysis courses, etc.

Here they are all in one place!

1/ Top 26 threads from the past 26 weeks of year


2/ How to build your Twitter


3/ The most simple set-up of Subasish Pani -


4/Free valuable tools that helps you to trader better!

More from Optionslearnings

MASTER THREAD on Short Strangles.

Curated the best tweets from the best traders who are exceptional at managing strangles.

• Positional Strangles
• Intraday Strangles
• Position Sizing
• How to do Adjustments
• Plenty of Examples
• When to avoid
• Exit Criteria

How to sell Strangles in weekly expiry as explained by boss himself. @Mitesh_Engr

• When to sell
• How to do Adjustments
• Exit


Beautiful explanation on positional option selling by @Mitesh_Engr
Sir on how to sell low premium strangles yourself without paying anyone. This is a free mini course in


1st Live example of managing a strangle by Mitesh Sir. @Mitesh_Engr

• Sold Strangles 20% cap used
• Added 20% cap more when in profit
• Booked profitable leg and rolled up
• Kept rolling up profitable leg
• Booked loss in calls
• Sold only


2nd example by @Mitesh_Engr Sir on converting a directional trade into strangles. Option Sellers can use this for consistent profit.

• Identified a reversal and sold puts

• Puts decayed a lot

• When achieved 2% profit through puts then sold

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.