October 2011 Archives

blog 3 subversion

| 5 Comments

In 3081W, this is my first time hearing of and using version control software, like Subversion.
So at the very beginning, I am not used to it at all. And it took me some time to get used to it. For example, for the first several labs, especially for the first lab using group repository, I was copying all the folders to the target directory and when I was trying to add the new folder and commit it, I met lots of troubles. It took me at least 3-4 hours to do submit that assignment. I went through all the errors like "file already exists" and other messages. It really drove me crazy when I got another new error and I had to look it up in Google or other websites. I finally got to know the hidden folder .svn. Finally I erased all the things in my repository and re-upload everything. It was really tough in the beginning.
After the struggle in the beginning, I gradually felt the convenience of using subversion. It provides us a useful way to share the code inside the group. Because everybody is busy and has lots of things to do, it is kind of hard to find a time to do the project together. And it is little hard to finish the task within a short time. So thanks to Subversion, it is possible to do the project separately. We can write some of the functions by oneself and merge the code with the help of svn. We can see each other's codes written by one person and download them to one's laptop to read or edit.
I haven't used the function of reviewing the previous versions. But I think that might be very useful. It prevents some mistakes from losing some of the codes or even the whole code.
To sum up, I think it is a good tool to help group members to be like a team. I may use it again in the future.

blog_02

| 8 Comments

Working in a group is quite different from working alone.
Of course, there are benefits: two guys are working together on the same project, so there will be diverse ideas on it and we have multiple choices on how to finish the task and we can determine which way is better and more effective.
Meanwhile, some difficulties come to us while doing the project. During the work on iteration 1, there are many challenged that come to me.
Firstly, I found that communication matters a lot in group work. When two or more people are working on a same project, making effective communication is one of the most important things in my opinion. If two guys have different opinions, the work will not be done efficiently. For example, before programming, several things must be clarified, such as the return value of a function and the arguments that a function calls. If these things are not matched, it will be a disaster. If is hard to change either of those after the whole job is done.
Secondly, I found that schedule management bothered us from doing the project effectively. Because we are taking different courses in this semester, and both are very busy, it is kind of hard to find a common time period to do the project together. In this case, it requires us to improve the efficiency within limited time.
In order to overcome these difficulties, we tried in this way. One of us worked out the framework of the program and we discussed about how to fill the functions into the framework together. Then each of us was responsible for writing some of the functions and then we combined them together. In this way, we used the time when we meet together quite effectively and some work could be done individually on one's own laptop. And it worked well. Because we had talked about how to write these functions and how would these functions work, we didn't have a hard time while combining them together.
By the way, I had really tough time while uploading out program to the subversion. I really struggled with svn commands and the hidden folder ".svn" and those errors like "xxx has already existed in this version". I spent like 3 or 4 hours to make it done to submit my programs, which made me really frustrated.
Anyway, it is fun on Iteration 1.

About this Archive

This page is an archive of entries from October 2011 listed from newest to oldest.

September 2011 is the previous archive.

November 2011 is the next archive.

Find recent content on the main index or look in the archives to find all content.