BC MV

@markminervini I use MarketSmith for scans. I look for their RS rating over 80 and weekly gains over 10%, along with market cap over 1 billion and daily trading volume over 300k. I run the scan daily, look at charts and pull names into a watch list. I then follow those stocks 1/

@maxmaster21 @markminervini I look at the history of the stock & see if it’s been honoring its 5 day, 10 day, 20 day, or other moving average. If it has been honoring one of those lines & it pulls back close to the ma of support or another level of prior support or resistance I buy if volume is light. 2/
@maxmaster21 @markminervini When I buy, I scale in and see if it’s working. I’ll usually give 1-3% of room beneath the support level before I cut it. I’d say I’m right less than but close to half the time. But my gains are bigger than 1-3% on average. I have very few positions (1-4) 3/3

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.