I will remember this upmove in bank nifty on 30th Nov ( Tuesday ) in my life.
@_GauravVashisth
@ITRADE191
More from Mitesh Patel
Few are saying that now a days I am not sharing any knowledgeable tweet.
I already shared in my old tweets and I don’t want to repeat same.
Read my old learning tweets in this PDF collection.
I already shared in my old tweets and I don’t want to repeat same.
Read my old learning tweets in this PDF collection.
Mitesh Bhai's tweets comprises of the live case studies. Study & apply them in your trading system.
— (DJ)itrade capital solution Private Limited. (@ITRADE191) June 25, 2021
Thanks to those who have made the pdfs of Mitesh Bhai's tweets, have merged it in this single pdf.\U0001f607\U0001f60e\U0001f607https://t.co/RLGACDY6sj
Once again a thread on breakout trades.
Future trading I am recommending to only those who have at least 25L capital to control risk management.
If less capital then do with cash or option writing.
Future trading I am recommending to only those who have at least 25L capital to control risk management.
If less capital then do with cash or option writing.
Boss is always Boss @Mitesh_Engr
— Aditya Todmal (@AdityaTodmal) July 31, 2021
Mitesh Sir's FUTURES BREAKOUT TRADES 101:
\u2022 How to pick stocks at right time?
\u2022 What to look for?
\u2022 Importance of BO post consolidation
\u2022 How to manage SL
\u2022 How to get huge profits
\u2022 Multiple Examples
In collaboration with @niki_poojary pic.twitter.com/7uXRgsLgtN
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.