Trimester Reflection

[NoraTheTurtle]

Team Gamers Reflection

Game Features (related commits linked)

• Pause Feature/Pause menu
• Skip Feature
• Score System
• Score backend connection to leaderboard

Technical Skills Applied

• OOP
• Class interactions
• Debugging multi-class systems
• Code integration across teammates' work

Team Management/Collaboration Growth

At the beginning of the trimester, I struggled with:

• Team members working independently instead of collaboratively
• Code pieces being built without integration planning
• Difficulty keeping project structure consistent

What I Learned

• How to divide work intentionally rather than randomly assigning tasks
• The importance of reviewing teammates’ code regularly
• How understanding others’ implementations improves overall design
• That successful teams require communication as much as good coding

I improved by:

• Splitting up work and forcing documentation to keep teammates organized
• Reading and understanding teammates’ code
• Encouraging shared work/collaboration
• Making sure features remained dynamic and interconnected instead of isolated

Connection to APCSA Unit Outlines

Using Objects & Methods

• Used objects to manage different parts of the game (player, score, pause system)
• Called methods across classes to control gameplay actions
• Practiced parameter passing and method organization to keep features modular

Selection & Iteration

• Implemented conditional statements for pause and skip functionality
• Used loops to continuously update gameplay and scoring
• Applied logical decision-making to control game flow and player interactions

Class Creation

• Designed and worked with multiple classes responsible for different game systems
• Learned how separating responsibilities improves organization and readability
• Reviewed teammates’ classes to understand structure and integrate features together

Data Collections

• Managed score tracking and stored game information dynamically
• Connected multiple game components using shared data
• Practiced organizing and accessing stored information efficiently across the program

Key Takeaways

• Writing code is only part of software engineering.
• Understanding other people's code is just as important as writing your own.
• Dynamic systems require intentional integration.
• Leadership in programming means enabling others to succeed while keeping the project cohesive.

Reflection

This trimester helped me grow both technically and as a team leader. I learned that successful software projects depend on communication, shared understanding, and intentional system design principles directly aligned with AP CSA learning targets