coding-cat-official/coding-cat

Tracking progress per problem

Open

#154 opened on May 25, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)TypeScript (2 forks)auto 404
good first issue

Repository metrics

Stars
 (2 stars)
PR merge metrics
 (PR metrics pending)

Description

  • Good way to mitigate against chatgpt. Problem solutions that are very often or always completed on first try are very suspicious
  • The positive way of framing this would be to simply track the number of problems solved on the first try. This number can be recorded clearly in the profile and submitted as part of the self-grading
  • A more sophisticated implementation would analyze finer grain details. Can we track time using the application? Or time between submissions? Any insights to be had there (and communicated to the user to help guide their practice?).

Contributor guide

Research direction
Explore the existing codebase to understand how user progress and problem data are stored. Identify the relevant frontend components and backend endpoints. Then design a tracking system for first try solves and time spent.
Tech stack
typescriptpython
Domain
full stack
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitTypeScriptPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50