I used to read all kinds of books, from self-help to fiction to programming. The more I read, the more knowledge I gained from one book to another.
After a long journey, I discovered that programming books and philosophy books are two types of books that are hard to understand.
Currently, I'm reading a book called "Flow" by Professor Mihaly Csikszentmihalyi, and it's amazing. It talks about the flow state in our lives, how we can use it, and how we can get into it quickly.
But when it comes to programming books like "Clean Code" by Uncle Bob, it's fantastic. It teaches everything you need to become a better programmer, and the message comes from the best programmers out there.
However, the lessons only work when you understand them. You need to already have a solid knowledge of the software field and use the lessons in your workflow. That's how you can effectively learn from programming books.
So ๐ธ๐ฉ๐บ ๐ฑ๐ณ๐ฐ๐จ๐ณ๐ข๐ฎ๐ฎ๐ช๐ฏ๐จ ๐ฃ๐ฐ๐ฐ๐ฌ๐ด ๐ข๐ณ๐ฆ ๐ฉ๐ข๐ณ๐ฅ ๐ต๐ฐ ๐ถ๐ฏ๐ฅ๐ฆ๐ณ๐ด๐ต๐ข๐ฏ๐ฅ? I think there are a few reasons.
๐๐ถ๐ฟ๐๐๐น๐, most programming books are written from one of two perspectives. Some are written for complete beginners, which is great for them. But others assume that you're already a professional-level programmer, diving into technical details that make advanced concepts more difficult.
๐ง๐ต๐ฒ ๐๐ฒ๐ฐ๐ผ๐ป๐ฑ ๐ฟ๐ฒ๐ฎ๐๐ผ๐ป is that programming itself is hard for many people. Working with numbers and staring at a dark screen requires a lot of brainpower, making it difficult for some to learn how to code.
๐๐ฎ๐๐ ๐ฏ๐๐ ๐ป๐ผ๐ ๐น๐ฒ๐ฎ๐๐, most technical people struggle to explain concepts to non-technical people. Even young programmers find it hard to explain basic concepts to others in the same field. As a result, technical books are often written for someone with a lot of years of experience. This brings us back to the first reason why programming books are typically written for professional programmers.
So, if you're new to programming and still want to learn more, my best advice is to start with simple documentation, tips, and tricks, and try to learn from mistakes.
Read technical books, but don't hesitate to reread them multiple times to get the most from any book you read.