Experience in online courses

I started my computer yesterday afternoon and habitually went to the csdn base camp to have a look. I found that there was just a network course at, so I went in after I went to the online client, which was very convenient.

Xu Mingfeng, a database instructor, talked about the topic "Practical Technology for software development by project instances", probably because it was a weekend and two o'clock during the day, there are not many people there, and there are only a few microphones for the students to listen to. I happen to have a few microphones, but the transmission of sound is still delayed on the Internet. I would like to say a word, it took me half a day to hear back from me. The teacher taught us somewhere in Dalian. I listened in a corner of Wuhan and discussed the problem with other students from Xi'an and Chongqing. It still works.

Well, let's focus on it. The teacher's lectures are mainly from a game named "Wuzi lianzhu". Don't associate this with wuziqi, there is a big difference between the two games. Originally, instructor Xu planned to use JavaCodeI came to give a lecture to us, but I suddenly found that we were all Java users, so I had to use the C code to explain, which mentioned the MVC development model, mr Xu is a database teacher, so he emphasized M as a data model. I have never heard of this idea before. I went to Baidu and found that Java is mostly used.

I haven't written Win32 for a long timeProgramSo when I saw that the teacher wrote so many functions and didn't see a class, I still felt quite unfamiliar. Process-oriented programming mainly aims to grasp the purpose and boundaries. The so-called purpose is the return value of the function, while the boundary refers to the function parameters. I recently learned a lot about C #, so all the code I write is classes. Basically, these process-oriented programs are not written, but the methods in the class are also functions. It is useful to listen to this lesson.

The course emphasizes testing and mentions such a development idea: "Use testing to drive programs ". The instructor's practice is to write a special function for testing, which I did not notice before.

The introduced game has a breadth-first advantage.AlgorithmThis is the knowledge in the data structure, and I forgot it. After reading the book, I picked it up again. This also illustrates the necessity of writing small projects!

The rest of the courses basically roughly explain code reconstruction and generate these ideas by using class libraries. I personally think it is not very clear. It is estimated that there are not many people attending the lectures with the teacher, few people communicate, so I feelSome are not good.

I entered the subject at half past one and ended the course at half past four. It took me three hours to listen to the loose knowledge and I still felt a little bit unworthwhile. This idea is probably because I am too quick and quick. The reason for this is not worth it. I think it is probably a matter of teacher interaction. teacher Xu said that courses without interaction are terrible, however, I found that too many interactions are terrible. For example, there are always people who don't know anything but pretend to know everything, and they keep asking boring and naive questions, A waste of time. Network-based special courses are different from those of systems. They are offered to people with a certain degree of foundation. Therefore, you need to listen to the opinions of those who have a basic foundation during interaction. The above only represents personal opinions.

After finishing the course, I also reflected on it. After all, it took me three hours to get a picture of what I learned. I still did not mention those things with high technical content. My expectation is too high. The teacher spoke very well, but I didn't expect it.

when talking to the C # instructor in our class at night, the instructor said, Are you still programming on weekends? I have discovered such a problem. It may be a weekend, so it is quite appropriate to explain that there is no technical depth, but it is very necessary at the macro level.