Today we're gonna talk about profits. They come from stock! #AdamSmith reminds us that stock is any resource paid for in advance when doing business. In general, profits and wages don't move together. (I.ix.1–2) #WealthOfTweets #SmithTweets
https://t.co/Is22ZUKwAE
More from @AdamSmithWorks
More from Trading
12 TRADING SETUPS used by professional traders:🧵
Collaborated with @niki_poojary
Here's what you'll learn in this thread:
1. Capture Overnight Theta Decay
2. Trading Opening Range Breakouts
3. Reversal Trading Setups
4. Selling strangles and straddles in Bank Nifty
6. NR4 + IB
7. NR 21-Vwap Strategy
Let's dive in ↓
1/ STBT option Selling (Positional Setup):
The setup uses price action to sell options for overnight theta decay.
Check Bank Nifty at 3:15 everyday.
Sell directional credit spreads with capped
@jigspatel1988 2/ Selling Strangles in Bank Nifty based on Open Interest Data
Don't trade till 9:45 Am.
Identify the highest OI on puts and calls.
Check combined premium and put a stop on individual
@jigspatel1988 3/ Open Drive (Intraday)
This is an opening range breakout setup with a few conditions.
To be used when the market opens above yesterday's day high
or Below yesterday's day's
Collaborated with @niki_poojary
Here's what you'll learn in this thread:
1. Capture Overnight Theta Decay
2. Trading Opening Range Breakouts
3. Reversal Trading Setups
4. Selling strangles and straddles in Bank Nifty
6. NR4 + IB
7. NR 21-Vwap Strategy
Let's dive in ↓
1/ STBT option Selling (Positional Setup):
The setup uses price action to sell options for overnight theta decay.
Check Bank Nifty at 3:15 everyday.
Sell directional credit spreads with capped
A thread about STBT options selling,
— Jig's Patel (@jigspatel1988) July 17, 2021
The purpose is simple to capture overnight theta decay,
Generally, ppl sell ATM straddle with hedge or sell naked options,
But I am using Today\u2019s price action for selling options in STBT,
(1/n)
@jigspatel1988 2/ Selling Strangles in Bank Nifty based on Open Interest Data
Don't trade till 9:45 Am.
Identify the highest OI on puts and calls.
Check combined premium and put a stop on individual
Thread on
— Jig's Patel (@jigspatel1988) July 4, 2021
"Intraday Banknifty Strangle based on OI data"
(System already shared, today just share few examples)
(1/n)
@jigspatel1988 3/ Open Drive (Intraday)
This is an opening range breakout setup with a few conditions.
To be used when the market opens above yesterday's day high
or Below yesterday's day's
#OpenDrive#intradaySetup
— Pathik (@Pathik_Trader) April 16, 2019
Sharing one high probability trending setup for intraday.
Few conditions needs to be met
1. Opening should be above/below previous day high/low for buy/sell setup.
2. Open=low (for buy)
Open=high (for sell)
(1/n)
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.