This document discusses collaboration tools and methods for software development. It describes tools the authors have used like Git and Bitbucket for version control and sharing code. It acknowledges they still need to learn advanced branching, conflict resolution, and proper merging with Git. It also mentions setting up UML diagrams, documentation standards, and bug tracking tools going forward to improve efficiency and reduce issues from working on shared code. The document ends by thanking the reader and opening the floor for any questions.
2. Overview
• Introduction / Why we needed this
• What we’ve done so far
• What we want to do in the future
• Question
3. Introduction
• Working together for 3 years
• Reached a certain level of efficiency
• Work on various non-school related projects
• Need for
• Developing more in less time
• Time is money
• Maximize efficiency
• Remove the time wasters and zero-productivity periods
4. The time wasters
• “Hey, can I have your updated part?”, “Here is my updated code for the backengines”, “Do you
still got that old version where …. ?”
• Missing files, incompatibilities, accidental rollover to older versions
• “What should I do next?”
• “What is this fooBar() function doing?”
• Especially after partial code merging
• “This part that you wrote is not working correctly when ….”
• Forget about the bug
• “OK.. Let’s merge the code”
• Things will break, will not fit, good code overwritten by dummy functions, split functionalities
6. Git and Bitbucket
• Things we can handle
• Commits/push
• Pull, clone
• Rollbacks
• Basic branching
• Tagging
• Still need to learn:
• Advanced branching
• Conflict resolution
• Proper merging