Skip to content

Recurring weaknesses appear as separate single-attempt entries #57

Description

@chenyu50

Description

The Recurring weaknesses section can show semantically similar entries as separate weaknesses, even when they appear to describe the same underlying problem across multiple interview attempts.

In my progress report, 26 weaknesses were listed and every entry was marked as occurring in only 1 attempt.

For example:

  • Develop a concrete algorithmic plan before attempting to write code.
  • Develop a systematic approach to problem-solving before writing code.
  • Practice articulating a step-by-step algorithm before attempting to write code.

These appear to describe closely related areas for improvement, but they are shown separately.

Steps to Reproduce

  1. Complete several interview attempts.
  2. Open the interview progress report.
  3. Check the Recurring weaknesses section.
  4. Observe semantically similar weaknesses being listed separately as 1 attempt.

Expected Behavior

Semantically similar weaknesses across multiple attempts should be grouped and counted by the number of attempts in which they occurred.

Actual Behavior

Semantically similar weaknesses are displayed as separate entries, each counted as 1 attempt.

As a result, the Recurring weaknesses section can contain only single-attempt entries even when similar feedback appears across multiple attempts.

Environment

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions