Hello and welcome to my profile.

This is a master thread of all the videos I've put up on my Youtube Channel.

I've shared plenty of learnings based on Option Strategies, Trading Psychology, Price action and other aspects of trading.

Will keep on updating this thread.

What is a Short strangle and how to do it the right way

Explained with live backtesting and adjustments

https://t.co/ggISI8N5Qd
Banknifty Weekly option strategy with adjustments.

Explaining the best way to execute this strategy to make 1% profit a week.

https://t.co/bL56TxtzrK
Nifty weekly option strategy with adjustments. Explained every detail in depth.

https://t.co/at09CZipcY
A safe strategy to play a bearish view with low risk, high reward

The right way to execute a bear put spread for maximum reward.

https://t.co/hcKnNUb6rT
How keeping random stoplosses can wipeout your capital.

https://t.co/yfAORegi5s
This is a problem that a majority number of traders face i.e Overtrading.

How to stop overtrading?

https://t.co/6z6z2Nun4E

More from Aditya Trivedi

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.