Error message explainer

The brief

Junior developers lose hours on error messages they do not understand. Build a chat app where they paste a stack trace or log and get a plain-language explanation, the likely cause and a suggested fix, with the cost of each answer shown. Good looks like: correct explanations on a test set of real errors, answers that admit uncertainty, and a cost per answer you can defend.

What you will build

1. Collect 50 real error messages with accepted fixes
2. Design a prompt that explains, diagnoses and suggests a fix
3. Compare a hosted model with a local one on your test set
4. Track tokens and cost per answer
5. Build a chat front end and write up the results

Free, open data to build it with

• StackSample: 10% of Stack Overflow Q&A ↗ Kaggle (Stack Overflow)

Check each dataset's licence before you publish your work. Your mentor gives your team its own version of the brief (data, scope or region), so every team's project is its own.