Personas and models
Lesson 5 of 10 · 3 min 46 s. Put the right kind of agent on each kind of work. Hand a question to a researcher and read its report, give slow tests to a test optimizer and read what it changed, put a small change on a cheaper model and see what Inherit means, then compare who did what and what it cost.
Before you start
- You have done Staying in the loop and are signed in to the console.
- A project connected to Jaah, with a Tasks list to open the new-task form from. The example is TimeSaver, a time-tracking app for small teams.
- Tests in the project, so there is something for the test optimizer to make faster.
Steps
- Open the new-task form in the project and write the question the way you'd ask a colleague. Ours is: Which features do the leading time-tracking apps for small teams offer that TimeSaver doesn't have yet? Not every piece of work is a change to the code; sometimes you need a question answered before you decide what to build.
- Open Advanced. Persona chooses who takes the work on. The coder, who builds changes, is the default; the others are each set up for one kind of work, such as a test optimizer, a translator, a prototyper that draws mockups, and a researcher, which reads, finds out and hands back a report with its sources. Pick Researcher. Then choose Unattended and press Go.
- When it's finished, open the task and go to Artifacts. The report answers the question feature by feature, names the apps it looked at and where each finding comes from, and ends with the gaps it thinks matter most. Nothing in the code has changed; the answer is the deliverable.
- On a new task, describe the slow tests in a few words. Ours is: Make the tests run faster. Under Advanced, pick Test optimizer, an agent that makes tests faster without testing any less. Choose Unattended and press Go.
- When it's done, open it and go to Details. Under Outcome, the test optimizer says what was making the tests slow, what it changed, and how it made sure they still check everything they checked before.
- On a new task, write the small change. Ours is: Add a tooltip to the Previous button on Reports that says Show the week before. Leave the persona as the coder and look at Model, under Advanced. It sets how capable, and how costly, the model behind the agent is. Inherit, the default, takes the tier the persona comes with, and the project's own setting only when the persona has none. For a job this small, set it to Low, the cheapest. Choose Unattended and press Go.
- Back on Tasks, read the three finished lines side by side. The end of each line says who did the work, a researcher, a test optimizer or a coder, and what it cost: to the dollar, or to the cent when it's under one. The small change on the cheapest model cost a couple of cents. Hover a cost for the exact figure.
What you learned
- Persona, under Advanced, chooses who takes the work on; the coder, who builds changes, is the default.
- A researcher answers a question and hands back a report with its sources under Artifacts; a test optimizer makes the tests faster without testing less, and explains what it changed under Outcome on Details.
- Model sets how capable, and how costly, the model is. Inherit takes the persona's tier, and the project's setting only when the persona has none; Low is the cheapest.
- The end of each task's line on Tasks says who did the work and what it cost.
Next
Next lesson: Keeping the list in order. Previous: Staying in the loop.
Related: