Wrote various systems, including:

• HUD elements

• Checkpoint system

• Dialogue system

• Audio system

• Level mechanics, including moving platforms, birds, and spikes

Wrote various editor tools, including:

• Level testing tool

• Build and submission tools

Maintained the git repository by reviewing pull requests and solving merge conflicts

Coordinated the building and submission of the game

Team specialization allowed for increased efficiency for the development team

Tools were prioritized early, allowing developers to be more efficient

Usage of design patterns, including the EventBus pattern and Finite State Machine pattern, allowed for cleaner code

Members were encouraged to add features they were passionate about rather than being restricted to specifications

Consistent communication allowed roadblocks to be solved quicker

Poor planning led to many pivots crunch later in development

Took many weeks to establish good git practices with the rest of the team, leading to increased merge conflicts

Task descriptions were not specific and relied on memories of previous discussions, leading to misunderstandings about requirements

Composing team members with different specializations resulted in a more efficient development process

Use design patterns to write cleaner code, where applicable

Define the core of the game earlier in development to reduce pivots and crunch

Clarify expectations on tasks with other members of the team before starting to reduce misunderstandings