Blog Post #3

This week, my capstone group worked on designing the project and splitting tasks among each member. It’s not the most exciting procedure, but I understand the necessity. Most of my personal coding projects have been done alone with no deadline, so there’s no point in breaking down a project into granular tasks. However, for a group project, I can imagine the coding conflicts if each programmer worked by themselves with minimal coordination. This actually happened during my first group project experience in another OSU course. A team member and I were working on separate features that eventually overlapped, resulting in wasted efforts and having to delete duplicate code. So while all this planning for my current capstone project is not my idea of a fun time, I’m glad my team was able to properly divvy up our responsibilities so that we can work efficiently towards creating a finished product. With that said, I’m excited to get into actual coding in the upcoming weeks.

Print Friendly, PDF & Email

Leave a comment

Your email address will not be published.