It is a tendency to interpret new information so that it becomes compatible with our existing theories.
Dis-confirming evidence must be seeked out to beat this theory.
He or she will not be the most popular member of the team, but definitely the most important.
Send an email to 10,000 people with stock market prediction by dividing them into 2 groups - telling reverse prediction to each group. Prediction for one of the groups will come true.
The fear of losing something motivates people more than the prospect of gaining something of equal value.
When it comes to compounding, dont trust your intuition - you have no idea how powerful it is.
99% Fat Free product seems more healthy than a product with 1% Fat.
There is no 3rd category of passive onlookers.
A Bill Gates monthly income in a group of 50 ordinary citizens can give an extremely misleading average.
And retweet the first tweet to share with others:
https://t.co/QYlZjIAGMD
10 Powerful Lessons of the book \u201cThe Art of Thinking Clearly\u201d
— Andrew Duggan (@ajdduggan) March 9, 2022
| Thread \U0001f9f5 pic.twitter.com/XzxUpBJGEL
More from Andrew Duggan
More from Books
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.