Master Coding.
Top 20 Best Coding Challenge Websites.
Thread 🧵
1. Do Retweet the first tweet.
2. Follow me on Twitter and turn on notifications: @mdjunaidap
Learn.
Build.
Sell.
I've Curated incredible tools and learning resources for developers, designers & content creators.
https://t.co/2XaQR6ASYw
More from Mohammed Junaid 🎯
Master Full-Stack Development for Free.
Thread 🧵
1. Mastering Frontend development:
2. Mastering Backend development:
If you enjoyed reading this thread,
1. Do Retweet the FIRST TWEET.
2. Follow me and turn on notifications: @mdjunaidap
🔥 700+ Tools & Resources for Developers, Designers, and Creators.
Learn.
Build.
Sell.
I've Curated incredible tools and learning resources for developers, designers & content
Thread 🧵
1. Mastering Frontend development:
Master Frontend Development for Free.
— Mohammed Junaid \U0001f3af (@mdjunaidap) May 22, 2022
Thread: \U0001f9f5
2. Mastering Backend development:
Master Backend Development for Free.
— Mohammed Junaid \U0001f3af (@mdjunaidap) May 31, 2022
Thread \U0001f9f5
If you enjoyed reading this thread,
1. Do Retweet the FIRST TWEET.
2. Follow me and turn on notifications: @mdjunaidap
🔥 700+ Tools & Resources for Developers, Designers, and Creators.
Learn.
Build.
Sell.
I've Curated incredible tools and learning resources for developers, designers & content
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.