To friends who want to be programmers (7) (8)

Http://news.csdn.net/news/newstopic/28/28081.shtml

From: programmer

(7) learning plan

--This learning plan is set by myself. I will share it with you for your reference and make progress together. 1. Computer composition principles

2. Operating System

3. Data Structure

4. Assembly Language

5. c

6. C ++

7. VC technology insider

8. Programming windows

9. in-depth introduction to MFC

10. Advanced windows

11. Inside the C ++ Object Model

12. Thinking in C ++

13. Objective C ++

14. Database

15. Network

16. Embedded OS and Programming

17. Hardware Microcontroller

18. NET and C #

19. Software Engineering

20. UNIX and Linux

(8) postscript

Over the past year, I have wasted a lot of time exploring, thinking, and detours. Until now, I still feel that I am a programmer. I have explained some of my experiences and ideas (of course, many of them are not necessarily correct. You are welcome to discuss them with us ), some suggestions and help may be provided to some friends who want to join the ranks of programmers. We hope to help these friends develop their programming skills.

If so, I will be very happy. Welcome Interested friends to send me e_mail (sjpsky@163.net); I have two hobbies, one is to read martial arts novels, the other is to make a hero.

Postscript: In this article, I used the analyster name to log on and post it on "csdn-program life". Many netizens read it and return it. I also received emails from several netizens, I am very grateful for your trust and encouragement.

What I want to explain is my article, which mainly aims to give some suggestions to "some friends who want to be programmers" and help them find a shortcut to self-training, (In fact, there are no shortcuts in the world. I think everything lies in understanding. The teacher leads the door and practices are personal. For example, I do not practice enough.) I do not do much useless work like I do. In addition, it is mainly a basic skill (personal opinion) that a programmer should possess. Some people call it "Internal merit", which I think is quite right. Without solid basic skills, how can we easily write high-quality and high-performance excellent programs?

Let's work together to revitalize our national software industry!