Skip to content

Criterias for instruction evaluation. #320

@RredCat

Description

@RredCat

Hi folks,

I am enjoying using instructions on my projects. However, I aim to assess the actual impact on GitHub Copilot.

I have read the topic - We need evals or something. But it will take time to implement, and frankly speaking, it will be too general (one project's trash is another project's treasure).

Do you have any criteria to evaluate the impact of instructions on a project?
I am tuning every instruction to the project's needs, but I don't know how to measure real impact.
I have instructed Copilot to respond in various human languages or adopt a Yoda-like tone. This impact is easy to spot.

Which criteria do you use to measure the impact of technical instructions?

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