I traded Tata Chem with 3x my normal position size today....Why ? Bcos of the setup. This is a setup i like a lot & have been successful 70% of the times - 3ib + NR7. If you get it on weekly it is even more powerful. Basically a price compression & waiting for spring action (1/n)

Secondly, today futures price O=L & wasnt broken in the 1st few mins which was like a confirmation. (A friend pointed out same wasnt true in cash, but it didnt matter then as volumes had started to build up)
Thirdly, price was resting at 21ema for the past few days and not (2/n)
ready to breakdown.
Fourthly, Max Ce Oi was @730 almost 10.93L which made the RR fantastic here.
Lastly, as per Dow theory - Price was making HH and HL's since beginning of May
If you think trading is easy & you can rely only on a single factor...think again ✌️ ( n/n)

More from Kool Aggarwal

More from Tatachemicals

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.