Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add same-topic historical comparison and progress to interview reports

Aperta
  • Qualcosa non va?
#393 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, rust
Ambito
analytics, frontend

Direzione di ricerca

Start by reading web/history.js to understand how completed reports and problem topics are stored, then inspect web/render.js and reportMarkup(...) for the report view. The issue also identifies web/practice-insights.js and tests under tests/browser/ as likely entry points. Done means showing same-topic metric and phase comparisons and resolved weaknesses, while handling first attempts and incomplete reports without changing storage or replay behavior.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Motivation

When a candidate finishes an interview practice session (for instance, solving a 1D Dynamic Programming problem), they currently receive an evaluation report in isolation. While CodeTrial tracks recent weak topics and offers a practice focus recommendation in the lobby, it does not provide direct feedback comparing the candidate's latest attempt with their previous attempts within the same category.

Without category-grounded comparison, candidates cannot easily tell whether they improved on specific recurring bottlenecks or whether previous weaknesses identified by the rubric were successfully resolved.

Proposed Solution

Introduce a client-side historical comparison section in the post-interview report view that compares the current report against the most recent completed report in the same topic or problem category.

The feature will:

  1. Identify the previous attempt sharing one or more problem topics from existing local/account history (web/history.js).
  2. Compute measurable deltas across key metrics:
    • High-level score and hint metric (coding score, communication score, hints count).
    • REACTO phase score progressions (frameworkAssessment.phases).
    • Weakness resolution: highlight which items from the previous attempt's improvementPlan were avoided in the current attempt.
  3. Suggest the next prioritized drill tailored to the category based on remaining or recurring weaknesses.
Expected Behavior
  • When a candidate finishes an interview and has at least one previous completed report in the same category/topic, the report view should display a "Category Progress & Comparison" card comparing the two sessions.
  • The comparison should show score changes (+/- deltas), hint differences, and phase score progression (Repeat, Example, Algorithm, Coding, Test, Optimizations).
  • Weaknesses from the prior session's improvementPlan that did not reoccur should be listed as resolved/improved.
  • When there are no prior attempts in that category, or if the current session was marked incomplete, the card should gracefully show that this is the first recorded session in the topic without errors.
  • Existing report rendering, replay view, and storage serialization contracts must remain completely unaffected.
Possible Implementation
  • web/practice-insights.js: Add helper functions to query recent history for matching topics, compute score and phase deltas, and reconcile previous improvementPlan items against current findings.
  • web/render.js: In reportMarkup(...), add a dedicated section to render the comparison table, resolved weakness checklist, and next targeted drill.
  • tests/browser/: Add unit tests verifying delta calculations, empty/first-attempt edge cases, and incomplete report handling.
Lingua principale
Rust
Stelle
177
Fork
100
Merge medio
1g 13h
PR unite (30g)
138

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di sysprog21/codetrial

Tutte le issue di sysprog21/codetrial

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.