Version Control Systems as a Student Collaboration Tool
And immediately to the point. Consider the idea of collaborative development of laboratory / coursework using github
Responsible student Peter creates a repository, for example, in the discipline "Parallel Programming", where in the first commit in the master branch a prepared project is available with the minimum of all that is necessary.
Then Petya creates a wiki where he puts the options for the whole group:
')
After that, Petya needs to add her classmates to the collaborators so that they can commit without a pull request (Pull Request):
Next comes the fun part - development! Each student creates his own branch (the name of which corresponds to the variant number) in the repository with the help of the git branch , where it will safely commit with pre-authorized devices for which it will be necessary to generate ssh keys and add them to your account settings on github:
Do you often need the help of your comrade, who sent you corrections to the code on the crochet and explained where the error is? Have you often asked for a “just look” code? Now the development has become easier, more interesting and faster.
What is the result?
Centralized and convenient place to store the code of all the options of the lab / coursework with a pleasant and convenient interface for viewing and syntax highlighting. The possibility of actually working together on one big project - for example, a term paper, which will speed up development at times.
Main advantages:
Minuses:
And if we add a resourceful teacher to all this, who will check the works (and everyone knows that you are exchanging code), looking at the source directly on the githaba ... And what, maybe it will be so soon. Or already have.
If the idea is old and has been widely used for a long time, I ask you not to shower rotten tomatoes, because good ideas always come late.
All nice design!
Responsible student Peter creates a repository, for example, in the discipline "Parallel Programming", where in the first commit in the master branch a prepared project is available with the minimum of all that is necessary.
Then Petya creates a wiki where he puts the options for the whole group:
')
After that, Petya needs to add her classmates to the collaborators so that they can commit without a pull request (Pull Request):
Next comes the fun part - development! Each student creates his own branch (the name of which corresponds to the variant number) in the repository with the help of the git branch , where it will safely commit with pre-authorized devices for which it will be necessary to generate ssh keys and add them to your account settings on github:
Do you often need the help of your comrade, who sent you corrections to the code on the crochet and explained where the error is? Have you often asked for a “just look” code? Now the development has become easier, more interesting and faster.
What is the result?
Centralized and convenient place to store the code of all the options of the lab / coursework with a pleasant and convenient interface for viewing and syntax highlighting. The possibility of actually working together on one big project - for example, a term paper, which will speed up development at times.
Main advantages:
- teamwork experience that will come in handy in the future;
- You do not need to carry the source on a flash drive (I wore some time on floppy disks). Do all universities already have internet ?;
- There is always an opportunity to see changes in your code (avoid situations “bliiin, captured the wrong version of the program on a flash drive ...”) and / or roll back to the desired revision (“damn, it worked yesterday!”);
- improving the quality of the code - classmates find a bug, hang up a ticket and discuss it here;
Minuses:
- Everyone will have to learn git / svn / hg, etc.
- Be prepared to use the repository by unscrupulous, selfish group mates.
And if we add a resourceful teacher to all this, who will check the works (and everyone knows that you are exchanging code), looking at the source directly on the githaba ... And what, maybe it will be so soon. Or already have.
If the idea is old and has been widely used for a long time, I ask you not to shower rotten tomatoes, because good ideas always come late.
All nice design!
Source: https://habr.com/ru/post/117852/
All Articles