More from Hardik Upadhyay, CMT.
#Infy is o/s at previous consolidation and trendline support.
Is it a beginning of a trend reversal or just a pullback?
I believe it's the former!
We'll find out tomorrow!
#Infosys #Q4FY21 #FY2021 https://t.co/faOahvcgPK
Is it a beginning of a trend reversal or just a pullback?
I believe it's the former!
We'll find out tomorrow!
#Infosys #Q4FY21 #FY2021 https://t.co/faOahvcgPK

Key reversal bar...#Infy pic.twitter.com/3GeYoty9KZ
— Hardik (@tradingwithdyr) April 12, 2021
On track to 5850...
As per traditional chart analysis, the breakout from the flag can extend by a distance of the flagpole which gives us the price objective of 5850 or thereabouts.
Let's see what happens!
#ApolloHospital https://t.co/jHgjR2WThe
As per traditional chart analysis, the breakout from the flag can extend by a distance of the flagpole which gives us the price objective of 5850 or thereabouts.
Let's see what happens!
#ApolloHospital https://t.co/jHgjR2WThe

Looks like a Flag to me...
— Hardik Upadhyay, CMT. (@tradingwithdyr) August 30, 2021
A flag pattern is a continuation pattern that suggests a short-term consolidation in opposite direction preceding a strong move.
A breakout above 4850 could have a rapid movement!#ApolloHospitals pic.twitter.com/q7g4enQjRY
More from Tataelxsi
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.