$TSLAQ Instead of having an accrual palooza, I will dribble these out as I have time and available information. The first account to be reviewed: Automotive Leasing Revenues. The remainder of the planet calls this Sales-Type Leasing (ASC 842.) (1/n)
More from Trading
A thread on getting intraday (any timeframe) data to excel without any coding. Limited to only last 60 days. Fetches from zerodha chart.
👇
1. Open the chart on zerodha web in chrome. Right click and select 'Inspect'. Click 'Network' as shown in this pic.
2. Right click on the last entry on the table you see and click 'copy as cURL (bash)'
3. Go to website https://t.co/f8rhwoGLUc and paste on the left box and click 'Run'
4. The output below candles written on right of box is the ohlc, volume and oi data. Copy and paste to excel.
👇
1. Open the chart on zerodha web in chrome. Right click and select 'Inspect'. Click 'Network' as shown in this pic.
2. Right click on the last entry on the table you see and click 'copy as cURL (bash)'
3. Go to website https://t.co/f8rhwoGLUc and paste on the left box and click 'Run'
4. The output below candles written on right of box is the ohlc, volume and oi data. Copy and paste to excel.
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.