admin/WebinarNotes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: initial commit of vault before dashboard work

Browse Source
This commit is contained in:
meels
2026-07-28 13:00:04 +02:00
commit b75730fda3
86 changed files with 7130 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

51
wiki/sources/2026-07-21-larysa-interview.md Normal file
View File

@@ -0,0 +1,51 @@
# Larysa Interview — Memory Loss, Phantom Integrations, and the Case for Skills
#source
## Source Metadata
- **Raw path:** `raw/sources/Larysa interview.md`
- **Source type:** interview conclusions/insights doc (auto-generated by Eugene's record→diarize→transcribe→summarize tool)
- **Participants:** [[eugene]] (SPEAKER_00, webinar host) and [[larysa]] (SPEAKER_01, technical BA/PM, ex-mobile developer)
- **Ingestion date:** 2026-07-21
- **Note:** closes the "Larysa not yet interviewed / PM use cases missing" gap opened in [[2026-07-14-nina-interview]] and [[2026-07-14-yulia-interview]].
## Core Claims
- **The friction with agentic AI is structural, not accuracy.** Larysa's blockers are not hallucination but (1) no durable memory across sessions, (2) integrations that look available and aren't, (3) over-eager drift on loosely specified tasks.
- **Agent memory, as shipped, is a net negative.** Eugene is blunt: "Memory is the worst thing agents have — it gives no benefit and confuses users to hell… it'd be better if it didn't [exist]." The replacement is [[skills-as-memory|skills]], not a better memory feature.
- **Claude starts work against capabilities it doesn't have.** It accepts a task, then discovers mid-way that a connector isn't implemented or isn't available for a *private* (vs. corporate) account — after half an hour of the user's time and tokens are spent. See [[integration-dead-ends]].
- **Consolidate, don't tool-hop.** Eugene's central pitch: one personal "operating system" where all project agents live together and can talk to each other beats spinning up Claude in separate folders — "my life just split into before and after."
- **Leave less room for imagination.** Under-specified prompts invite drift, and the drift causes collateral damage you won't notice. Standardized procedures (skills) are the constraint. See [[leave-less-room-for-imagination]].
- **AI-assisted coding is production-ready as of ~Claude 4.6, with carve-outs.** "Code isn't something elite anymore… though authorization and payments I still wouldn't trust to Claude."
- **Diarization + role inference is the differentiator** in interview automation over plain transcribe-then-summarize.
## Key Evidence / Details
- **Larysa's actual usage** (unusually deep for a non-engineer role): opens pull requests, wires Claude to **ClickUp** (Jira analog) and **Figma**, builds clickable prototypes, writes user stories and tests.
- **The dead-end example:** a Teams bot to watch a work chat and auto-create ClickUp tasks. Verdict — Teams is effectively a dead end (Microsoft exposes no usable external API); Slack has first-class Claude support from Anthropic but needs a paid seat she isn't given. Figma is blocked the same way: no personal paid account → no full editable access.
- **Her quote on the failure mode:** "That's not hallucination exactly… it just first goes looking for what you don't have. I don't know how to fight this." — left explicitly unresolved.
- **Model choice:** Eugene runs **Claude 4.7** in production, finding **4.8 "too proactive"** ("without the flights of fancy 4.8 has").
- **Testing note:** prefer browser/web testing over emulator testing with Claude — the emulator got badly stuck.
- **Tool convergence:** both participants independently landed on recording and auto-processing interviews. Eugene's system adds speaker diarization plus *role* inference from conversation context ("Speaker 0, HR Equity Lead; Speaker 2, Senior Programmer") — ~10–11 min for a one-hour interview. This document is its output.
- **Webinar commitment:** [[skills-as-memory|skills]] are the one topic Eugene commits to covering for Larysa.
## Connections
- Entities: [[eugene]], [[larysa]], [[claude-code]], [[inspectron]], [[virtido]] (Larysa's affiliation tentative)
- Concepts: [[skills-as-memory]], [[integration-dead-ends]] (new), [[leave-less-room-for-imagination]] (new), [[harness]], [[levels-of-ai-usage]], [[solve-first-then-skillify]], [[code-as-throwaway]], [[personal-ai-operating-system]]
- Companion interviews (same webinar-scoping series): [[2026-07-14-nina-interview]], [[2026-07-14-yulia-interview]]
## Open Questions
- How to reliably pre-empt integrations Claude recommends that aren't available for the user's account type — stated as unsolved by both participants.
- Is a Teams-triggered auto-task bot feasible at all given Microsoft's API surface? (Asserted dead end, not demonstrated.)
- How to get full editable Figma access without a personal paid account.
- Is 4.8's "over-proactivity" a model property or a prompt-specification problem? (It reads as the same drift [[leave-less-room-for-imagination]] blames on loose specs — Eugene treats it as the model's fault.)
- Larysa's employer is never stated; [[virtido]] is inferred from the interview series. Status: tentative.
- Webinar structure and scheduling — deferred to a follow-up with [[yulia]].
## Change Impact on Wiki
- Created [[larysa]] (entity); created concepts [[integration-dead-ends]] and [[leave-less-room-for-imagination]].
- Updated [[skills-as-memory]] (memory-as-anti-feature: the negative case for why skills exist), [[harness]] (consolidation-over-tool-hopping claim), [[code-as-throwaway]] (the auth/payments trust carve-out), [[levels-of-ai-usage]] (Larysa as a high-rung user still missing the skills rung), [[solve-first-then-skillify]], [[claude-code]] (4.7 vs 4.8; memory and connector limits), [[eugene]], [[yulia]], [[virtido]], [[overview]].