"Three modes of evolution have thus been brought before us: evolution by fortuitous variation, evolution by mechanical necessity, and evolution by creative love." - C.S. Peirce 1893
More from Carlos E. Perez
Programming in abstractions is very different from a system that is capable of its own 'abstracting'. But what does abstracting mean? We only know of its inputs and outputs, but we fail to describe its inner workings.
I like this short video about living in space. This is because it makes you realize the gaps in your knowledge when you turn off something (i.e. gravity) that you have always assumed to be present.
Perhaps we can understand 'abstracting' better if we turn of many assumptions that we unconsciously carry around. Perhaps we need to get rid of the excess baggage that is confusing our thinking about abstraction.
Turning off gravity and living in space is a perfect analogy. We somehow have to turn off a cognitive process to understand the meaning of abstraction.
The first step to divorce ourselves from our habitual cognitive processes is to realize the pervasiveness of 'noun-thinking' .
I like this short video about living in space. This is because it makes you realize the gaps in your knowledge when you turn off something (i.e. gravity) that you have always assumed to be present.
What does living in space do to the human body? pic.twitter.com/kzIlEEr7pp
— Tech Insider (@techinsider) December 20, 2020
Perhaps we can understand 'abstracting' better if we turn of many assumptions that we unconsciously carry around. Perhaps we need to get rid of the excess baggage that is confusing our thinking about abstraction.
Turning off gravity and living in space is a perfect analogy. We somehow have to turn off a cognitive process to understand the meaning of abstraction.
The first step to divorce ourselves from our habitual cognitive processes is to realize the pervasiveness of 'noun-thinking' .
More from History
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.