#Mahlog Undergoing a Volatility Contraction near its ATH area.
Probable ABC breakout and triangle formation in #PnF
@srvithal388 @flyingvikas129
More from Aditya Shyam Jalan
Finally started moving 🌟 A VCP breakout
#Nifty #Happstmnds #Trading #PnF
It was also discussed in #ChitChart by @rajran06 sir.
@Definedge
#Nifty #Happstmnds #Trading #PnF
It was also discussed in #ChitChart by @rajran06 sir.
@Definedge
#HAPPSTMNDS 1%
— Aditya Shyam Jalan (@Aditya_Jalan_3) August 17, 2021
In line with the bullishness of the IT sector. Consolidated after a good upmove, providing a very low risk entry point .
CR entry at 1427
SL as the next probable Triple Bottom Sell at 1344.85#PnF #Trading #Process #StockMarket #StocksToWatch @Definedge pic.twitter.com/k76ViohZF2
@srvithal388 Sir, same thing happened with me, Stop was triggered bcoz of Intraday Move and I decided to enter again by taking the CR, but missed the bus.
Even though bus was missed , I feel delighted bcoz I followed the #process
Even though bus was missed , I feel delighted bcoz I followed the #process
#Deepakntr Super Pattern after a brief consolidation at ATH.
— Aditya Shyam Jalan (@Aditya_Jalan_3) July 7, 2021
Count clusters till two decimal points.@srvithal388 @flyingvikas129 pic.twitter.com/5SFLEmz0Ia
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.