WebinarNotes/wiki/overview.md

Overview

#overview

Top-level synthesis and navigation for this vault. See index for the full content catalog.

Purpose

A high-signal personal knowledge base. raw/ holds immutable source materials; wiki/ holds LLM-authored, continuously maintained pages. The current corpus is webinar-prep material on how AI is reshaping software engineering, likely authored by eugene (Status: tentative).

The through-line

Across thirteen sources — six talks/videos/interviews from practitioners (two of them Theo's), five interviews conducted for this project, a business-facing short, and one quantitative outside study (swepr) — one spine recurs:

As the cost of writing code goes to zero, value migrates from producing software to directing and verifying it — and the durable human assets become judgment, ownership, taste, and in-person relationships.

Everything else hangs off that:

• The machine side — how the work gets done now: the harness (universal agent + small toolset + loop), skills-as-memory, the tooling progression evolution-of-agent-tooling, and agentic-loops — all governed by context-as-scarce-resource. The non-engineer's version is Allie's personal-ai-operating-system.
• The human side — what stays yours: product-ownership over outcomes, connections-as-moat as the last non-commoditized asset, seniority-and-the-junior-squeeze, and the need to decoupling-identity-from-profession.
• The strategy side — where to point it: think-wider-not-bigger, treat code-as-throwaway, and mind enterprise-ai-reality (the company-managed-harness market). Theo's second video supplies the verifying half of the spine its method: make-more-cheap-code — keep hand-verification of what ships, and generate orders of magnitude more never-shipped code to verify and explore.
• The frontier side — what it looks like at the far end, from thorsten-ball at amp (99% of their code AI-written): shedding-weight by deleting every process that only existed because humans were the bottleneck; build-for-the-agent-not-the-human; work async-by-default in remote sandboxes and ask for proof rather than claims. His two mechanisms for software becoming personal — emacsification-of-software and explosion-of-internal-software — are the corpus's strongest outside validation of the webinar's own thesis, "little tools you make for yourself." He is also its sharpest dissenter: he uses no skills, no MCP, no slash commands. Both mechanisms now carry a sourced counterweight — maintenance-is-the-real-cost: writing code was never the bottleneck, maintenance is, and an internal service is a second business. The reconciliation is a threshold, not a winner: tiny personal tools pass, replacing your Jira does not.
• The adoption side — what goes wrong when organizations try this, from nikolai-sheiko's multi-company casework (2026-07-30-rakes-in-ai-sdlc-adoption): the SDLC collapses around the humans — review-is-the-new-bottleneck and volume metrics (LoC, PRs) go anti-informative, so measure completed tasks without rework; the developer's job flips from CPU-bound coding to developer-as-agent-manager; and the winning company move is not custom AI development but installing and evolving a standard harness (enterprise-ai-reality) — with skills grown by walking the agent through real tasks and verified by a context-free subagent (solve-first-then-skillify).
• The demand side — three interviews ground it all in a real audience. The two HR ones (2026-07-14-nina-interview, 2026-07-14-yulia-interview) supply pain points (interview write-ups, job descriptions, sourcing) that collapse into "a candidate knowledge base plus search," teachable via levels-of-ai-usage and solve-first-then-skillify. Their key finding: adoption is blocked by friction, not resistance. The 2026-07-21-larysa-interview adds the advanced user's version of the same story: past the friction, the remaining walls are structural — no durable memory, integration-dead-ends, and drift on loose specs (leave-less-room-for-imagination). Her diagnosis matters because she is technically deep yet skipped the skills rung, which is exactly what her "the agent forgot" complaint reduces to.

See ai-agent-evolution for how the capability curve got here.

Where sources agree vs diverge

• Agree: code is cheap/disposable; harnesses are the unit of work; skills-as-memory (Konstantin ↔ Allie ↔ Eugene); human relationships rise in value (Sebastian ↔ Allie ↔ Eugene, who lands there independently in the Yulia interview); solve-first-then-skillify (Eugene ↔ Konstantin's heuristics); context is the constraint — Thorsten's version is the bluntest: the dominant variable in output quality is the information you put in, not the model or the effort level. The 2026-07-22-ai-is-stupid independently compresses the machine-side spine into a business one-liner: model + context + harness = employee-level answer. Slop is a human problem, not an AI defect (Theo ↔ Thorsten, from verification discipline and from taste respectively). Software becomes personal — "little tools you make for yourself" (Eugene's webinar arc ↔ Thorsten's club app and bespoke forks ↔ Allie's personal OS). And the corpus's central stakes claim now has outside measurement: 2026-07-30-stanford-swepr-widening-gap finds the productivity gap between AI-mastering and lagging teams grew 4.8% → 19% (4×) from April 2023 to July 2025 — Allie's prediction, measured; the same study's codebase-size finding independently supports context-as-scarce-resource. 2026-07-30-rakes-in-ai-sdlc-adoption cites that same Stanford chart as his stakes slide and lands on the spine independently — "companies no longer need custom AI development, install Claude Code or Codex and configure it" is harness-over-model as a service playbook, and his codebase-stores-context prescription converges with Thorsten's from the opposite direction. His review-bottleneck casework (+1% net despite more PRs) is SWEPR's +91%-review-time finding told anecdotally.
• Diverge: personal vs company-managed vs vendor-managed harness (eugene vs sebastian vs amp); online vs in-person networking (Eugene/Sebastian); OSS as marketing vs OSS growth; built-in agent memory as anti-feature (Eugene) vs persistent context docs used without complaint (Allie); tight specs (leave-less-room-for-imagination) vs wide latitude (think-wider-not-bigger); agent diff-summaries as sufficient review (Theo/Dax) vs invisible drift as the core danger (Eugene); model choice as a real lever (Eugene runs 4.7 over 4.8) vs a distraction past the frontier (Thorsten); local consolidated workspace (Eugene) vs local dev disappearing into remote sandboxes (Thorsten); build-your-own-tools (thorsten-ball, the webinar arc) vs maintenance-is-the-real-cost (the vibe-coding video, with the corpus's only observed reversal: an in-house Jira clone abandoned for Linear in four months); permit opting out of the agent-manager switch (nikolai-sheiko — "don't force everyone") vs the gap is irreversible and compounding (allie-miller, swepr) — see developer-as-agent-manager. These live under "Contradictions" on the relevant pages.
• The one that matters most for the webinar: thorsten-ball runs a 99%-AI-written codebase with no skills, no MCP servers and no slash commands — his context lives in the codebase and AGENTS.md. That is the corpus's first credible rejection of the mechanism the webinar's central promise rests on. Three readings (situational / premature abstraction / same thing under another name) are logged on skills-as-memory; none is settled. The evidential asymmetry that favoured him narrowed on 2026-07-30: nikolai-sheiko is a second practitioner voice on the pro-skills side — his "Agentic Evolution" (guided tasks → agent writes the manual → context-free-subagent verification) is the corpus's first described test of a skill, though his cases are anonymous anecdotes where Thorsten's is first-hand daily practice at scale.

Navigation

• index — content catalog
• Sources (13): 2026-07-14-everything-we-knew-about-software-has-changed · 2026-07-14-gap-between-ai-users-irreversible · 2026-07-14-sebastian-eugene-interview · 2026-07-14-skills-based-on-git · 2026-07-14-nina-interview · 2026-07-14-yulia-interview · 2026-07-21-larysa-interview · 2026-07-22-ai-is-stupid · 2026-07-24-youre-reading-way-too-much-code · 2026-07-28-agentic-engineering-10x-developer · 2026-07-29-what-if-we-vibe-code-it · 2026-07-30-stanford-swepr-widening-gap · 2026-07-30-rakes-in-ai-sdlc-adoption
• People: theo-browne · allie-miller · sebastian · eugene · konstantin · nina · yulia · larysa · thorsten-ball · nikolai-sheiko
• Tools/orgs: claude-code · amp · hermes · virtido · inspectron · swepr
• Concepts: see the through-line above (27 pages) · Timeline: ai-agent-evolution · Comparison: theo-konstantin-allie

Open Questions (vault-level)

• How does an individual build a professional network from a standing start? (Cross-source; the emotional center of the Sebastian interview.) — Tentative protocol drafted at network-from-a-standing-start; validation instrument at 2026-07-14-network-from-standing-start.
• Reusable templates for Allie's 3 foundation docs — a concrete webinar deliverable?
• Should the webinar docs be ingested to connect the corpus to the deliverable? Resolved 2026-07-28: they live in raw/notes/ as authored deliverables, not sources, and are cited as raw where used. (HR Contacts.md, named in the original question, does not exist in the vault.)
• Can the transcribe→summarize tool integrate with Manatal (the HR team's ATS)? And is a paid HR-system build going ahead? (Both open from the HR interviews.)
• How should a user pre-empt integration-dead-ends? Both participants in the Larysa interview left this explicitly unsolved — the corpus's only wholly unanswered technical problem.
• Does the skills rung actually fix cross-session and cross-project memory, or only per-procedure recall? The webinar's central promise rests on this.
• Are skills necessary at all, or a 2025 scaffold? thorsten-ball ships at the frontier without them. The corpus has never run the cheap test that would separate the readings — the same task, with and without a skill, in a non-engineer's hands. See skills-as-memory.
• Who pays for the token budget at fleet scale? (Scoped 2026-07-28.) For individuals the answer is settled and unremarkable — one subscription; the corpus's heaviest users (eugene, 7 parallel agents on a $200 plan; allie-miller, ~100 agents) report no ceiling, and the AI divide stays a skill gap. The open question is metered/fleet pricing and enterprise allocation — plus whether eugene's price-rise prediction reopens it. See enterprise-ai-reality.
• If forms and admin panels die (build-for-the-agent-not-the-human), what does a non-technical person actually operate? "Prompt the agent" presumes exactly the competence the HR interviews identify as the bottleneck.