Top 10 Tallest Gopurams of Temples in India.
1. Sri Ranganathaswamy Temple, Srirangam, Tamil Nadu. Height - 239.5 ft.
More from All
The best morning routine?
Starts the night before.
9 evening habits that make all the difference:
1. Write down tomorrow's 3:3:3 plan
• 3 hours on your most important project
• 3 shorter tasks
• 3 maintenance activities
Defining a "productive day" is crucial.
Or else you'll never be at peace (even with excellent output).
Learn more
2. End the workday with a shutdown ritual
Create a short shutdown ritual (hat-tip to Cal Newport). Close your laptop, plug in the charger, spend 2 minutes tidying your desk. Then say, "shutdown."
Separating your life and work is key.
3. Journal 1 beautiful life moment
Delicious tacos, presentation you crushed, a moment of inner peace. Write it down.
Gratitude programs a mindset of abundance.
4. Lay out clothes
Get exercise clothes ready for tomorrow. Upon waking up, jump rope for 2 mins. It will activate your mind + body.
Starts the night before.
9 evening habits that make all the difference:
1. Write down tomorrow's 3:3:3 plan
• 3 hours on your most important project
• 3 shorter tasks
• 3 maintenance activities
Defining a "productive day" is crucial.
Or else you'll never be at peace (even with excellent output).
Learn more
How to be 5x more productive.
— Ben Meer (@SystemSunday) August 1, 2022
A best-selling author\u2019s 3-3-3 Method:
2. End the workday with a shutdown ritual
Create a short shutdown ritual (hat-tip to Cal Newport). Close your laptop, plug in the charger, spend 2 minutes tidying your desk. Then say, "shutdown."
Separating your life and work is key.
3. Journal 1 beautiful life moment
Delicious tacos, presentation you crushed, a moment of inner peace. Write it down.
Gratitude programs a mindset of abundance.
4. Lay out clothes
Get exercise clothes ready for tomorrow. Upon waking up, jump rope for 2 mins. It will activate your mind + body.
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.