Some advice to people who study computer science

College English-don't feel funny. I highly recommend this course because reading without a professional document is unthinkable. Chinese translation often comes out in the SE years, but now many publishers simply directly to the e-text printed up. The way to learn is to force themselves to see the original textbooks, the beginning will not understand, with a lot of natural proficiency. It is absolutely necessary for any industry to eat hard and be cruel.

Computer architecture and assembly language-the books on architecture are all over the land, and the same is true, but there is a very good book in the compilation. "80x86 assembly Language Program Design Course" (Tsinghua University Press, black cover, Yang Ziwen). You need to focus on the design of the 386 protection mode. Otherwise you will learn some things at the bottom of the modern operating system when you think it is looking at the heavenly book.

Computer operating system principles-our development is always on a specific operating system, if not, only one possibility: you implement an operating system on your own. In any case, the operating system principle is required to read. This is just like when we make peripherals for a chip, the basic work sequence of the chip must be understood. There are a lot of books in this category, and I don't see which one is very outstanding. I just think that after reading these books, if you are free, you should see "Inside Windows 2000" (Microsoft Press, I read the e-text version, the Chinese title must be the Windows 2000 technical Insider, etc.).

Data structure and algorithms-this course can determine a person's level of programming, is a core curriculum. My first choice is the Tsinghua version (Zhu Shi, Liu Tianxi). A lot of people like to buy C + + version, but I think it is not necessary. C + + syntax makes the algorithm implementation process more complex, and many teachers like to use the module to make the algorithm more complex. But after learning the C version of the book again to browse the C + + version of the book is the best.

Software Engineering-This course is more and more important to discover it later on, although it is as unintelligible as a horse-chul at first. My advice is to see "Practical Software Engineering" (Yellow, Tsinghua). Don't spend too much time remembering rules and jumping over them if you can't read them. After each time you have completed a Software design task (whether it is practice or work) to review the review, each will have a harvest.

Windows Programming-"Peking University Press, Petzold" I suggest anyone who attempts to design a Windows program to learn the VC carefully before learning it. And the front of the "Inside Windows 2000" is also best to be read in the back of this book. In this book, there is no C + +, no GUI, no controls. Some are how to use the original C language to complete Windows programming. After learning it, you will find that VC is really easy to learn. Do not read this book in advance before you learn VC, you'd better not touch. Many of the schools I know have even used it as a teaching material. Visible its importance.

The above courses I think are important lessons (if you want to be a Windows programmer).