And here it is:
The 3 most important rules which I follow in spotting a major trend reversal laid out in this stock, 'as it is'.
1. Trend reversal
2. Price patterns
3. Indicator confirmation
Perfect TA chart.
All boxes ticked !!
Do comment, like and share !!!
#DRREDDY https://t.co/4JGg71GenE
Today at 2 pm:
— Kunal Bothra (@kbbothra) July 5, 2022
I will bring to you one of the SUPER FINEST TECHNICAL CHART setup on a largecap name.
Agar yeh nahi chal paya toh kuch nahi chal paayega\u2026
Retweeet tsunami has to come for this one\u2026 #stock #breakout #technical
More from Kunal Bothra
Crude Oil prices likely to taper below $100…
Interesting Derivatives Data…
Interesting Derivatives Data…
#MarketsWithETNOW | Is the #crude concern overblown? What do the charts indicate? What will be the trend going forward? Watch to find out as @kbbothra analyses #Brent #Crude #Oil #StockMarket pic.twitter.com/4SBSfpiKmd
— ET NOW (@ETNOWlive) June 1, 2022
More from Screeners
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.