Not every trade works out for me. Far from it! I lose half the time. But EVERY trade is a good play at the time, because my risk is always a fraction of my likely reward. And that's the secret... I always get odds on my money. In trading, that's the definition of a "good choice."
In any performance business the bottom line is winning, hitting the goal, getting the job done. Winners do what they have to do to win. Losers make excuses why they didn't perform. A way to win and a way to lose ALWAYS exists. It's a matter of the quality of the choices we make. pic.twitter.com/RXvu4o4FBC
— Mark Minervini (@markminervini) April 15, 2021
More from Mark Minervini
Visualize what you expect to happen and how you will react. More importantly.. see in your mind what can go wrong and how you will react. Make this routine contingency planning.
According to your 3rd book, could you please explain how to practice visualization in trading? @markminervini
— KoRn (@kornkonthorn) July 24, 2021
More from Markminervinilearnings
Compounding is amazing. Just 3 months into the year I'm having one of my best returns. That's because instead of arguing with the market, I made an adjustment and took what it was offering, and that allowed for rapid turnover that can add up pretty fast if you are concentrated.
Short term trading is what has worked best in this market. Until I see an alternative working better, I'm going to stick what is working like a charm.
— Mark Minervini (@markminervini) April 14, 2021
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.