Apollo Hospital👇 https://t.co/3TReZvM53C
Next Tweet on stocks for 1-4 weeks
— Pramod Sharma\U0001f549\ufe0f\U0001f1ee\U0001f1f3 (@itspramods) April 14, 2022
All will be my top bet
Working start now.
Disclaimer: Not a recommendation at all.
More from Pramod Sharma🕉️🇮🇳
Conditions
rsi >50
RSI avove ma60
Price above ema 60
It is for indicators lovers.. i see rarely but as per my experience enough setup if one is follow with descipline
rsi >50
RSI avove ma60
Price above ema 60
ITC
— Pramod Sharma\U0001f549\ufe0f\U0001f1ee\U0001f1f3 (@itspramods) March 29, 2022
Try this combo RSI 60 period on 60 min chart
Backtest and tell me result.
Rsi/ma crossover abovev50 level pic.twitter.com/In3xrgWQz0
It is for indicators lovers.. i see rarely but as per my experience enough setup if one is follow with descipline
More from Divis
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.