Administration

What Yavaren has learned

Lessons Yavaren learns from your own work and uses in your next jobs; see the evidence, switch them off, edit or revert them.

Yavaren learns from your work the way a new team member would. When the same thing goes wrong again and again, it writes itself a short lesson and uses it in your next jobs straight away. Examples:

• "Run the database migrations before the tests in this repository."
• "Reviewers here often comment on tests: add or update tests for every behaviour you change."
• "Tests here depend on the time zone: run them with TZ=UTC."

Lessons stay inside your organisation. They never apply to another customer.

Where lessons come from

A lesson needs repeated evidence: the same thing seen at least three times, in at least two different jobs, within a month. The evidence comes from:

• the checks of each story: a failing check, a check that already fails on your main branch, a missed part of the definition of done, a set-up problem in the error output;
• your approved rules that were broken;
• the code reviewer's findings on Yavaren's pull requests;
• what happened to the pull request: merged, closed, reverted, changes requested;
• what your reviewers wrote on Yavaren's pull requests;
• changes you asked for in a plan;
• low ratings you gave a job.

A lesson applies where the evidence came from: one repository, a stack, a project or the whole organisation. When the same lesson appears in several repositories, it also applies more widely.

What you see

Open What Yavaren has learned in the navigation. You see:

• This week: what Yavaren learned, which lessons helped, which it retired, and fix rounds per job with and without lessons.
• Each lesson: where it applies, how sure Yavaren is, how many jobs used it, and whether it helps, with the numbers. For example: "the problem came back in 0 of 5 jobs with this lesson, against 3 of 4 before it".
• Evidence and history for each lesson: what it was learned from, every wording it had, and who changed it.

Under a job's Details you see the lessons that job was given.

What you can do

Managed by Yavaren. On Yavaren cloud, lessons and the learning level are looked after by the Yavaren team: you can read every lesson, its evidence and its effect, and ask for a change through Services & support. The actions below are the ones the team takes for you. (An on-prem installation may give them back to its customers' own people.)

Where your organisation manages its own lessons, members can:

• Switch off a lesson. No job gets it from now on. Switch on brings it back, including a lesson Yavaren retired.
• Edit a lesson to put it in your own words. The earlier wording is kept.
• Revert a lesson. An edited lesson goes back to its previous wording. A new lesson is undone: no job gets it, and Yavaren does not learn it again by itself.

Admins can also pause learning for the whole organisation.

How Yavaren checks itself

Yavaren keeps measuring each lesson. A lesson that does not help is retired automatically, with the reason. So is a lesson that no job has used for a long time.

A lesson is advice for the coding assistant and nothing more. It never changes your rules, the checks that run, or what the assistant may do. Text that reads like an instruction or a command is refused.

Your data

Your learning level applies. At off, Yavaren records nothing and gives no lessons. Only at full does it keep short excerpts of comments and errors, with credentials removed. Changes to Yavaren's own instructions for all customers are made only by Yavaren staff, after review.