o-ni

o-ni

Tuesday, October 11, 2011

blog assingment 2

i decided to write about the advantages rather then disadvantages of team programing. i haven't really found any disadvantages to team programing that subversion won't deal with satisfactorily. the only foreseeable problem is that both partners would try to work on the same code with two different approaches.

as for the advantages, it's always better to work in teams. the golden rule of computer programing is 'if you don't know something, the guy on the right probably does', and just having another pair of eyes on your code can help find errors that to the author are no short of baffling. not to mention that you don't have to do the work that your partner does.

i am assuming that the partner is halfway competent here...

the partners can also work together by focusing on what each does best, like logic, syntax, testing, debugging and bringing the chips and drinks, all important aspects of coding and rarely all mastered by a single person. also, for something like the logic of the program, another person may have a different and perhaps better idea. even a novice programmer can help improve the program just by sharing a different look on the logic with the team.

a program that would be a horror to do alone, even with a single partner, suddenly becomes much easier.

3 comments:

Christopher Jonathan said...

I like your golden rule of Computer Programming. I'm also talking about the advantage of working together rather than the disadvantages. On the other hand, I think the disadvantages that you are talking on the paragraph 1 is not the one that the question ask. I think it is more like the software issue.

Christopher Jonathan

lucasa24 said...

I agree and like your idea of golden rule of computer programming. This is definitely one of the most significant benefit that everyone can obtain from team programming: Your partner can give you a better idea on how to work something out and vice versa, provided that you both are constantly communicating well with each other and are comfortable working with and helping each other out.

Lucas Low

Huy Tran said...

I agree with every advantage you discussed: bug spotting-code reviewing, cutting half of the workload and making better program by picking the best of many approaches.

The problem you mentioned is not very hard to solve though. If we divide the work clearly, especially when based on modular design of the software, chances are we never have to touch the partner's code.

BTW, I like your idea about drinks and chips.

-Huy Tran