Rubberduck

An immediate answer can fix a symptom while leaving the developer unsure why the code failed. Rubberduck explores whether a conversation can help someone identify the gap in their own reasoning.

The project direction is question-first debugging: ask about expected behavior, observed behavior, and the assumptions connecting the two before offering a hint. The goal is to keep the developer involved in diagnosing the issue.

Questions add friction. Too many can slow someone down; too few can turn the companion into another answer generator. The case centers on finding when to ask, when to offer a hint, and how much context is enough.

The portfolio documents this as a project in progress. It does not yet include a released implementation, user study, or measured improvement in debugging outcomes.

Evaluate the question-first flow on concrete debugging tasks. Look for whether users can explain the cause afterward, how quickly they reach a useful hypothesis, and where questions become repetitive. These are evaluation goals, not reported results.