Sharing here a strategy that gave me most consistent profit in intra-day in all these years. Narrow Range break out / break down.

Here's how i scan the stocks :

- 3ib
- 3iib
- NR7+IB
- NR14+IB
- NR21+IB
- Double Doji

Stock Selection Criteria :

- IB/Smaller Doji range is around 1%
- Beta is above 0.75
- How has the stock performed in the past with this strategy

Entry :
- Long/Short on Previous Day High/Low break

Stop Loss :
- Opposite side of previous day candle

Target :

1%, 2%, 3%
Will post my stock selection here as and when i can as i have seen that in spite of sharing every single rule, people are still not getting the stocks selection correctly.

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.