Some Ideas about software discussion groups in Universities

This was first proposed by Dr. Ma of our team. The general idea is that we hope that students in the software team can have an opportunity to communicate with each other, learn from each other, and drive each other.

Later, Dr. Chen expressed support and started preparing for this issue. I also hope that the members of the team can create such an academic atmosphere. I have worked hard before and learned some lessons and ideas, post it and give your comments.

In fact, I have also tried the method of student report. It should have been Dr. Chen's time at the degree Center of the Ministry of Education. At that time, the graduate students with the software direction and the students with the undergraduate tutor system did this, at that time, every student reported a question once a week. After the report was completed, I felt that the effect was not good. Basically, the students read the PPT and later improved a little. Each person designed an experiment, let's take a look at it. The content of the students with good final results is too difficult, and the content of the students with poor foundations is too easy. The overall learning atmosphere is not created. Lesson: all the students in the software direction listen to one piece of content. This one-size-fits-all approach is unrealistic. The reason is simple: the basic differences between students are large and there is no common language, no matter who gives the lecture, it is a type of "destruction ". My idea is: programming is not done first, but in middle school. My suggestion is: task-driven-teacher push, students do. The instructor takes the lead and the students take the lead. Divide the students into several groups, and each group has a balance between good technology and poor technology. The teacher splits the tasks of the projects that our team has completed or not completed, discuss and learn Based on tasks. Each instructor has one or two groups. The group-based discussion is organized once a week or every two weeks. The Group reports their progress and describes key technologies, create a competitive atmosphere. I named this method: the overall planning of the market economy system. The upper-level teachers should plan the resources of the time just like the planned economy, so as to promote and supervise the resources. The lower-level teachers should give full play to students' initiative, learn independently, and discuss independently, key questions: teachers participate in decision-making. For example:

In the last six months, I have brought a few Undergraduates with network and computer skills. I am working on a project (mobile phone base station positioning, the program is divided into three parts, one of which is the Android mobile phone end, one is that the socket side receives data from the mobile phone side, and the other is that the Web Side calls Baidu map to display the location). You can always find fields of interest. Based on students' interests, I divided them into two groups, mobile phones and servers, skilled students are responsible for some key technologies and the overall architecture. Technically poor students are responsible for checking information and Writing Test Programs (basically, they can be found online, a ready-made program can be changed). Every day, a report is reported (the program submits SVN and checks). The progress is checked every week. Up to now, the results are good. Basically, a project can be completed, in some places, it is better to achieve it than I do, and the overall ability of students can also be improved. Personal thoughts are for reference only.