0808.2024.Today I Learned

Sungju Kim·2024년 8월 8일

Sparta_Coding_Camp_TIL

목록 보기
12/53

Team Project Intro

We were asked to build a java program that can manage student course registration along with their course grades.

Link to our project github

Linkt to our project presentation slides

Team Reflection

The team reflected on their Java project, identifying areas they did well, encountered problems, and areas for improvement in future projects. They also assessed their performance using KPIs. Here's a summary:

Problems Encountered

  • Sungju (me): Insufficient use of interfaces, lack of refactoring, and inadequate planning of data structures.
  • Hyunjung: Issues with object-oriented programming (OOP), UML diagrams, and documentation (e.g., taking screenshots during merges or when encountering issues).
  • Geon: Coding without prior design (due to a template) and low utilization of polymorphism.
  • Daehyun: Poor OOP practices (e.g., low-level encapsulation) and insufficient use of inheritance, interfaces, and polymorphism. Real-time PR reviews were effective but questioned for efficiency.
  • Cheolhee: Lack of consistency in outputs and delays in merging PRs.

Things to Improve (Next Try)

  • Sungju (me): Sketch out object-oriented designs before coding and get tutor feedback regularly.
  • Hyunjung: Set specific checkpoints for taking documentation screenshots and share them with the team. Ensure PR approvals happen quickly (within 5 minutes). Share issues with team members as they arise.
  • Geon: Improve OOP practices and focus on better design.
  • Daehyun: Study OOP principles more deeply and improve project design skills.
  • Cheolhee: Collaborate as a team to plan OOP strategies from the start, document issues, and prioritize immediate code reviews and merges.

Actions Moving Forward

  1. Share problems with the team immediately and work on solutions together.
  2. Predefine checkpoints for documentation and share them with the team throughout the process.
  3. Create both data structure and class diagrams prior to coding.
  4. Hold meetings focused on improving OOP practices, including addressing issues like lack of polymorphism and encapsulation.
profile
Fully ✨committed✨ developer, always eager to learn!

0개의 댓글