A Guide to Reading Technical Books for Engineers: Turning Knowledge into Skills
Technical books are essential for engineers aiming to improve their skills. However, many people struggle with issues like 'I bought it but couldn't finish it' or 'I read it, but the content didn't stick.'
In this guide, we will introduce effective reading methods that focus on 'connecting to skills' rather than 'reading through' a technical book. We will explain practical techniques and mindsets, so please use this as an opportunity to rethink your own reading style.
Why do technical books feel difficult?
First, it is important to understand that feeling 'technical books are difficult' is natural. The reasons include the following:
There is a lot of content that is hard to visualize without practical experience
They are written assuming the reader has a certain level of prerequisite knowledge
There is a large volume of information, and many abstract concepts appear
Furthermore, because many technical books prioritize 'academic accuracy,' they tend to feature redundant expressions and frequent technical jargon. This becomes a major hurdle for beginners.
How to read technical books to connect them to skills
Clarify your purpose
The first important step is to clarify the purpose of 'why am I reading this book?'
Do you want to learn a new language?
Do you want to deepen your understanding of a framework?
Do you want to learn design principles?
If your purpose is clear, you may decide that you don't need to read everything, making it easier to select what to read. Articulating your purpose also serves as a guide when you get lost while reading.
Don't try to read everything from the beginning
You don't need to read everything in order from the start. In fact, it is more efficient to focus on the necessary chapters or knowledge.
Use the table of contents to choose themes that are necessary for you right now
Read only the important chapters carefully
Since many technical books are in a format that allows for 'skimming' like reference books, try to adopt a flexible reading style to reduce any sense of intimidation.
Read in conjunction with practice
Combining input and output deepens your understanding.
Try out the code examples from the book yourself
Summarize what you have read in your own words
Organize the content as if you were explaining it to someone else
By being conscious of the "read → try → read" cycle, the retention rate of your understanding will increase significantly. It is also effective to have opportunities to immediately apply the knowledge you have learned in your work or personal development projects.
Read while taking notes
Don't be afraid to write notes in the book; it is highly recommended.
Underline parts you think are important
Write down questions or insights in the margins
Use sticky notes so you can look back at them later
By switching from a "just reading" mindset to a "dialogue with the book" approach, the learning effect will be significantly enhanced. If you are using e-books, it is also a good idea to make use of highlight and note-taking features.
Don't aim for perfection
There is no need to try to understand everything. It is difficult to grasp the entire content in a single reading.
Skip parts that you don't quite understand
Accept that you "couldn't understand it now, but will come back to it later"
The world of technology changes rapidly, and trying to understand everything is not realistic. Rather, a stance of "rereading when it becomes necessary" is important for consistency.
Have a place for output
It is also recommended to share what you have read on blogs or social media. Outputting has the following benefits:
You can objectively confirm your level of understanding
You can gain new perspectives from reader feedback
It becomes easier to retain in your memory
There are many platforms suitable for technical sharing, such as Qiita, Zenn, and note. Even if it is a small article at first, it is important to write in your own words.
What kind of technical books should you choose?
While how you read is important, "which book to choose" at the beginning is also extremely important. When beginners or intermediate learners are choosing, it is good to pay attention to the following points.
Does it cover themes close to practical work?
Are the explanations thorough, and are there plenty of diagrams and code examples?
Is it appropriate for your level? (Are there too many technical terms?)
Also, the following checkpoints are useful.
Is the sample code published on GitHub?
Is the first edition recent? (Is the information fresh?)
Review ratings on Amazon or technical social media
Reputation and reviews are helpful, but whether it is "content you need right now" is more important than anything else. When in doubt, try reading a sample or browsing through it to see if it feels right for you.
Technical books are too valuable to just read and be satisfied. To connect them directly to your skills, it is important to read "with a purpose," "while working with your hands," and "flexibly, only the parts you need."