4 keys to my success:
1. I wait for easy dollars while the amateurs fight for hard pennies.
2. I get aggressive when amateurs doubt the setups.
3. I take profits when amateurs get greedy and hysterical.
4. I religiously manage my risk while amateurs hold losers.
More from Mark Minervini
The word is sacrifice. You are not going to be the best at day trading, swing, value and growth investing. It will be amazing if you can master just one. And you only need one. So pick one and sacrifice the rest! There is no other way unless you want to suck at a bunch of things.
What is the single unavoidable thing you must do to be the best or great at one thing? One word?
— Mark Minervini (@markminervini) April 14, 2021
Oil, copper and other commodities came under heavy selling pressure today and that's a good thing because it's mounting evidence that inflation may be peaking.
Positive signs on inflation include fertilizer prices peaking and trending downward. Used Car prices are also down (which led inflation). The recent price break on the $XLE - which emerged almost to the day the market topped, could be an indication that we are close to a low. pic.twitter.com/2MtcKjjmAz
— Mark Minervini (@markminervini) June 23, 2022
More from Markminervinilearnings
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.