Team Work Experience

So far, I have done many projects, both individually and as a team, which I have learned many things from and I want to talk about them all in this post.

Individual Work

Individual work has disadvantages such as:

• The bigger the project is, the developer’s focus and sensitivity on different parts of the project will decrease.
• There is no competitive challenge and cooperation with other programmers, thus the development process may be exhausting.
• To bring different parts of the project to a nearer standard,  programmer needs to have consultation with other developers.

These problems and many other factors make the developer gain a richer experience in Team Work.

Team Work

In my opinion, team work has much more advantages than individual work, because the programmer has the chance to get to know other programmers, share technical information mutually, and measure his work level in comparison to others.

If he is more mature and experienced than other programmers, he should share his knowledge with them, and on the contrary, if he is working with more experienced programmers, he can benefit from their experiences and coding ideas.

Of courser, if there is no accurate management on team works and if no version control management for project like GitHub, Gitlab or BitBucket is used, many problems will arise during project development.

For instance, if in a web design project, more than one developer is working on the front-end, it is possible that both have made changes on a single file, in this case a project manager is needed to specify the tasks of each programmer so that conflicts of modification on same parts of the project be minimized, and also there’s a need for project and version control management system that if several developers make changes on the same part, it could be possible to merge changes and resolve conflicts through the system.

Pair Programming

Related to team work, there is a technique called pair programming, which is related to agile project management method, so that two developers work together on the same system, one is responsible for coding and the other is responsible for checking and evaluating the other one’s code. Detailed description about pair programming can be found here.