My experiences in trading through various international locha events, high VIX and various events.
A thread
Never works
Use lower volumes and bigger stops to counter the volatility
VIX is an annualised number. A 23.5 VIX means the market is expecting a 23.5% move on the Nifty from here in the next one year with 68% confidence
The number of trading days in a year is 252, sqroot of that is 15.87
( 16 rounded, what we call rule of 16)
1.3% of current Nifty is tomorrow's implied move = 225 points
At say 14 VIX, 14/16 = 0.87 , implied move = 147
So, in high VIX, the intraday moves are large. One may not need to keep overnight positions and just trade intraday for large rewards, the moves are expected to be there
But at high vol, another factor of volatility comes into play, PERSISTENCY
PERSISETNCY simply means if vol is high today, it will be high tomorrow also
"Smooth seas never made skillful sailors" - African Proverb
--------------------end ------------------
https://t.co/bDjwnNt8D5
More from Subhadip Nandy
Two year back thread on MFI, someone liked this so came up in notifications . Rather than running around 100s of indicators, I have made this my go to indicator under any circumstances and have been using this for years
This thread actually had some great answers , one can learn a lot about the thought processes of different traders from the answers. Please go thru them
What do you think/use as the most robust leading indicator if following technical analysis ? Please answer with reason , I will provide my answer after 2 hours
— Subhadip Nandy (@SubhadipNandy16) August 12, 2019
( At Delhi airport , bored as hell )
This thread actually had some great answers , one can learn a lot about the thought processes of different traders from the answers. Please go thru them
More from All
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.
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.