From: http://blog.solrex.cn/go/622676.html
These two weeks are the course selection audition period, and the course has not yet officially started, so when I am a little idle, I have switched over the Uinx environment advanced programming (Advanced Programming in the Unix environment, 2e ), after reading seven or eight chapters, I found that this book is really worthy of the title of "Unix programming Bible. The book gives a very systematic and detailed explanation of the problems that may be encountered in programming, especially when you see the problems you have encountered before, it's just an epiphany, I just want to sigh, "Oh, that's it! ".
I usually writeProgramWhen you encounter problems, you always turn to Google for help. For those books that talk about programming skills, they have never caught a cold (especially those written by Chinese people). They always feel that such books are not suitable to take time to read them carefully.This type of problem-driven learning is fast and efficient in solving a specific problem, but it is also often limited by the difficulties of being invisible. After a problem is solved, you still need to search for answers to other similar problems.
Problem-driven learning will lead to insufficient system and in-depth understanding of the problem.But if you just take this big part and finish it slowly, it will be boring, and the experience is not deep. I think the best way to read a programming book is to first have a certain amount of practice and then read a book, and keep exercise andCodeThe number of exercises. Sometimes you may want to look at the instance code first and then the text explanation. If the code understands it, check whether the author's explanation is the same as what he understands. If the Code does not understand it, the attention to the text will be deepened. And sometimes read those entry-level textbooks, you may wish to read only the code.
Of course, when programming, there should be several classic books on the table for reference as a manual. It is good to repeat some chapters from time to time. Like apue, I think it is very suitable as a case book. programmers who develop Linux/Unix will never be disappointed to buy one.