Inspiration

This project was inspired by the way developers naturally collaborate while solving Data Structures & Algorithms (DSA) problems—discussing logic, catching mistakes, and debating better approaches. Combining that with the social deduction mechanics of games like Among Us led to the idea: what if debugging itself became the gameplay? Instead of fixing a spaceship, players fix a broken problem statement while trying to identify who’s secretly sabotaging it.

What We Learned

We explored how problem-solving, collaboration, and game design intersect. Key learnings included:

Translating technical tasks (debugging, optimizing) into engaging gameplay

Designing mechanics that reward logical thinking and communication

Understanding how subtle errors in logic, constraints, or complexity can change outcomes

Applying algorithmic reasoning such as time complexity:

T(n)=O(nlog⁡n)vsO(n2) T(n)=O(nlogn)vsO(n 2 )

and how these differences influence decision-making in real time

How We Built It

The project was structured around three main components:

Game Logic: A multiplayer system where crewmates collaboratively fix a DSA statement while an imposter introduces incorrect logic, edge cases, or misleading constraints.

Problem Engine: Predefined and dynamic DSA prompts with modifiable constraints, test cases, and expected outputs.

Discussion & Voting System: After each round, players analyze changes, debate reasoning, and vote out the suspected imposter.

We focused on making technical problem-solving accessible and interactive, rather than purely competitive.

Challenges We Faced

Balancing gameplay: Ensuring sabotage was subtle enough to be believable but not impossible to detect

Difficulty tuning: Designing DSA problems that are engaging without overwhelming players

Collaboration vs. chaos: Preventing discussions from becoming unstructured while keeping the game fun

Fair detection mechanics: Making sure imposters couldn’t be identified too easily based only on skill gaps

Edge cases: Handling scenarios where multiple “correct” solutions exist or where ambiguity appears in constraints

This project ultimately showed how learning, coding, and game design can merge into a social experience—turning debugging from a solitary task into a shared, strategic challenge.

Share this project:

Updates