# Eugene

#entity

## Summary

Senior software engineer (20+ years, ~20 commercial; computer vision, embedded/firmware, Edge Compute/IoT at [[inspectron]]), content creator, and builder of a custom [[claude-code|Claude Code]] [[harness]]. Author and presenter of the webinar *"From a chat box to your own operating system"*; interviewer of [[sebastian]], [[nina]], [[yulia]], and [[larysa]]. Champions "bring your own harness" and building small AI tools for yourself.

## Current Understanding

Eugene argues every developer should build a personal harness because knowing every detail makes it far more effective; he demoed one (Telegram-like UI, one agent per project, inter-agent messaging, per-agent memory, "done thinking" signal). His stated unsolved problem — building a professional network — is what makes [[connections-as-moat]] the interview's emotional center; notably, in [[2026-07-14-yulia-interview]] he independently lands on the same residual ("the human's role is just to be human — introductions, communication").

Heavy Claude user on the **$200 max plan**; ran 7 project-agents in parallel; built the record→diarize→transcribe→summarize tool whose output *is* the two HR interview raws. Teaches [[levels-of-ai-usage]] and [[solve-first-then-skillify]] as the non-programmer curriculum. Predicts AI prices rise, not crash ("what I now buy for 200 will cost about 1,000"). A paid build of the HR candidate-base system for Yulia's team is on the table.

**Positions sharpened in the [[2026-07-21-larysa-interview|Larysa interview]]:** built-in agent memory is an anti-feature, not an unfinished one ("it'd be better if it didn't [exist]") — [[skills-as-memory|skills]] replace it; consolidate into one workspace rather than tool-hopping ("my life just split into before and after"); [[leave-less-room-for-imagination|leave less room for imagination]], which is also his critique of build-a-whole-project-in-two-prompts demos. Runs **Claude 4.7** in production, avoiding 4.8 as "too proactive"; considers AI-written code production-safe from ~4.6 but withholds **authorization and payments**. Claims his diarization + role-inference pipeline is the real differentiator over plain GPT transcription, which "only guesses who spoke."

**Likely identity:** Eugene appears to be the **owner/author of this vault** and of the webinar being prepared. Status: **tentative but strengthened** — both HR interviews name him as the webinar's author/presenter and the tool-builder; the raw `Ideas for webinar.md` notes share his references.

## Evidence

- Interview: BYO-harness demo, tools (Conductor for git-worktree isolation; references [[hermes]]), projects **insin** (apt-get-style edge updater) & **Keller**, the ~6-month networking blocker — [[2026-07-14-sebastian-eugene-interview]].
- Webinar author/presenter, Inspectron, one-button interview tool, 7 parallel agents, English-first webinar titled *"From a chat box to your own operating system"* — [[2026-07-14-nina-interview]].
- $200 max plan, levels ladder, solve-first method, price-rise prediction, paid HR-system offer, manager/subordinate framing — [[2026-07-14-yulia-interview]].
- Memory-as-anti-feature, consolidation pitch, imagination/drift principle, 4.7-over-4.8, auth/payments carve-out, diarization+role-inference claim — [[2026-07-21-larysa-interview]].

## Related Pages

- Entities: [[sebastian]], [[nina]], [[yulia]], [[larysa]] (interview counterparts), [[inspectron]] (employer), [[virtido]] (webinar audience)
- Concepts: [[harness]], [[connections-as-moat]], [[product-ownership]], [[decoupling-identity-from-profession]], [[levels-of-ai-usage]], [[solve-first-then-skillify]], [[leave-less-room-for-imagination]], [[integration-dead-ends]]
- Tools: [[claude-code]], [[hermes]]

## Contradictions / Uncertainty

- Disagrees with Sebastian: BYO-harness vs company-managed; OSS as marketing vs growth; LinkedIn/content vs in-person networking.
- Vault-owner identity is inferred; confirm before treating as fact.

## Next Questions

- Concretely, how does Eugene build a connections network from a standing start? (The interview's biggest open question.)
