Here are 7 of the best programming books you should read:
If you want to be successful in programming, open this:
Here are 7 of the best programming books you should read:
"Countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way."
Standout from the crowd by mastering the art of clean code.
https://t.co/GL1rWdk9z7
Overtime programs become "inefficient and hard to maintain and extend".
Which is why refactoring is just as important a skill as coding itself. This book covers the process in depth.
https://t.co/2445beyEgr
This is a fundamental topic in programming.
"[This book] covers a broad range of algorithms in depth, yet makes their design and analysis accessible to all levels".
https://t.co/skWBffVdog
"Widely considered one of the best practical guides to programming".
This book is packed with strategies to help programmers w/ debugging, refactoring, minimise code complexity & more!
https://t.co/mzcxBiLcOi
"This book is packed with practical advice-about everything from estimating and coding to refactoring and testing."
https://t.co/yvjwWA6kR1
"[This book] covers topics ranging from personal responsibility and career development to architectural techniques for keeping your code flexible and easy to adapt and reuse."
https://t.co/lZJNhU2kMN
What's the use of being a skilled coder if you crumble in technical interviews?
This book has helped countless of programmers land jobs.
https://t.co/Mj3L4eGFRA
Building projects or contributing to open source are the best ways to implement what you’ve learned.
I simplify software development and getting into tech💡
Follow @NikkiSiapno for more free tips and free resources.
If you enjoyed this thread, don't forget to like, comment, and retweet the first tweet. https://t.co/8Gx8NXtK03
If you want to be successful in programming, open this:
— Nikki Siapno (@NikkiSiapno) November 1, 2022
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
![](https://pbs.twimg.com/media/DrIk2JhU8AAjf_m.jpg)
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
![](https://pbs.twimg.com/media/DrIk3TjU0AAhf3D.jpg)
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.