2 days earlier, you were what you were. 2 days later, you are what you are. Nothing has changed.
Thank you for reading.
The markets crashed yesterday, and they surged today.
Here are 10 things I learned.
Grab a 🍿.
More from Screeners
Opposite is happening now. IHNS, double bottom, +ve RSI divergences, etc are failing badly for permanent reversal. Level up your SAR game to stay in the game on both sides.
#bearrun
#BearMarket
#bearrun
#BearMarket
Head & Shoulders pattern, double top and bearish RSI divergences fail more often in bull market and generally gives a very good SAR trade. Vice versa is also true for bear market.#bullrun #BullMarket
— Aakash Gangwar (@akashgngwr823) February 9, 2021
You May Also Like
1/ Some initial thoughts on personal moats:
Like company moats, your personal moat should be a competitive advantage that is not only durable—it should also compound over time.
Characteristics of a personal moat below:
2/ Like a company moat, you want to build career capital while you sleep.
As Andrew Chen noted:
3/ You don’t want to build a competitive advantage that is fleeting or that will get commoditized
Things that might get commoditized over time (some longer than
4/ Before the arrival of recorded music, what used to be scarce was the actual music itself — required an in-person artist.
After recorded music, the music itself became abundant and what became scarce was curation, distribution, and self space.
5/ Similarly, in careers, what used to be (more) scarce were things like ideas, money, and exclusive relationships.
In the internet economy, what has become scarce are things like specific knowledge, rare & valuable skills, and great reputations.
Like company moats, your personal moat should be a competitive advantage that is not only durable—it should also compound over time.
Characteristics of a personal moat below:
I'm increasingly interested in the idea of "personal moats" in the context of careers.
— Erik Torenberg (@eriktorenberg) November 22, 2018
Moats should be:
- Hard to learn and hard to do (but perhaps easier for you)
- Skills that are rare and valuable
- Legible
- Compounding over time
- Unique to your own talents & interests https://t.co/bB3k1YcH5b
2/ Like a company moat, you want to build career capital while you sleep.
As Andrew Chen noted:
People talk about \u201cpassive income\u201d a lot but not about \u201cpassive social capital\u201d or \u201cpassive networking\u201d or \u201cpassive knowledge gaining\u201d but that\u2019s what you can architect if you have a thing and it grows over time without intensive constant effort to sustain it
— Andrew Chen (@andrewchen) November 22, 2018
3/ You don’t want to build a competitive advantage that is fleeting or that will get commoditized
Things that might get commoditized over time (some longer than
Things that look like moats but likely aren\u2019t or may fade:
— Erik Torenberg (@eriktorenberg) November 22, 2018
- Proprietary networks
- Being something other than one of the best at any tournament style-game
- Many "awards"
- Twitter followers or general reach without "respect"
- Anything that depends on information asymmetry https://t.co/abjxesVIh9
4/ Before the arrival of recorded music, what used to be scarce was the actual music itself — required an in-person artist.
After recorded music, the music itself became abundant and what became scarce was curation, distribution, and self space.
5/ Similarly, in careers, what used to be (more) scarce were things like ideas, money, and exclusive relationships.
In the internet economy, what has become scarce are things like specific knowledge, rare & valuable skills, and great reputations.
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.
