2.9 KiB
Larysa
#entity
Summary
Technical business analyst / project manager and former mobile developer; interviewed by eugene as the project-management voice in the webinar-scoping series (alongside nina and yulia). The most technically deep non-engineer in the corpus — and the one whose frustrations are most structural.
Current Understanding
Larysa is a power user by any reasonable measure: she opens pull requests, wires Claude to ClickUp (a Jira analog) and Figma, builds clickable prototypes, and writes user stories and tests. She is enthusiastic but worn down — not by wrong answers, but by two failure modes that cost her time and tokens:
- No memory between sessions. She explains something one day; the next day it is gone and she re-pays for the explanation. This is her stated core problem.
- integration-dead-ends. Claude confidently starts a task, then discovers the connector isn't implemented or isn't available for her private (vs. corporate) account — half an hour in. "I don't know how to fight this."
Her blocked builds are instructive: a Teams bot that would watch a work chat and auto-create ClickUp tasks (Teams offers no usable external API); Slack (first-class Claude support, but needs a paid seat she isn't given); full editable Figma access (needs a personal paid account).
Diagnostically she sits high on levels-of-ai-usage — well past chatbot, acting on real files and systems — but without the skills-as-memory rung, which is exactly why her pain reads as "the agent forgot." Skills are the one topic Eugene committed to covering for her in the webinar.
Evidence
- Role, tooling (ClickUp/Figma/PRs/prototypes/user stories/tests), memory complaint, integration dead-ends, Teams/Slack/Figma blockers, emulator-vs-browser testing note — 2026-07-21-larysa-interview.
- Flagged twice as an un-interviewed gap before this ingest — 2026-07-14-nina-interview, 2026-07-14-yulia-interview.
Related Pages
- Entities: eugene (interviewer), nina, yulia (same interview series), virtido (affiliation tentative), claude-code
- Concepts: integration-dead-ends, skills-as-memory, leave-less-room-for-imagination, levels-of-ai-usage, solve-first-then-skillify
Contradictions / Uncertainty
- Name is taken from the raw filename and the summary's speaker label; spelled "Larisa" in earlier notes. Status: tentative.
- Employer never stated; virtido inferred from the shared interview series. Status: tentative.
Next Questions
- Does the skills rung actually resolve her memory complaint, or is her problem cross-project context (which skills don't solve)?
- Would her employer supply the paid Slack/Figma seats if a working prototype existed — i.e. is the blocker technical or budgetary?
- What was her BA/PM pain point in yulia's original three-item list, and does it match what surfaced here?