Files

EugeneTes 3314112bb9 ingest: Stanford SWEPR widening-gap study and AI-in-SDLC adoption pitfalls

Add two new sources with summaries, new concepts (developer-as-agent-manager,
review-is-the-new-bottleneck), new entities (SWEPR, Nikolai Sheiko), and a
query on the Stanford source; update related concept pages, overview, index,
and log.

2026-07-31 08:33:56 +02:00

4.4 KiB

Raw Permalink Blame History

Levels of AI Usage

#concept

Summary

Eugene's ladder of AI adoption, mapped for the webinar: web chatbot → built-in memory → Claude Code/Cowork with local file access → CLAUDE.md → skills → Obsidian knowledge base → RAG. Most people are stuck at level one; the practical ceiling for non-programmers is CLAUDE.md + skills ("that's your maximum").

Current Understanding

The ladder is a diagnosis tool and a curriculum at once. Each rung adds persistence and leverage: memory makes the chat remember, local file access makes it act, CLAUDE.md makes instructions durable, skills-as-memory make processes reusable, a knowledge base makes answers compound, and RAG only matters at corporate scale. It is the structural skeleton of the planned webinar ("From a chat box to your own operating system" — the title itself names the bottom and top rungs) and the practitioner's version of Allie Miller's personal-ai-operating-system: her foundation-docs + skills + proactive workflows land at the same CLAUDE.md-plus-skills plateau.

Supporting practices at the plateau: keep CLAUDE.md self-maintaining ("always keep CLAUDE.md up to date"), narrow the variability of interpretation when prompting (leave-less-room-for-imagination), and solve-first-then-skillify.

The ladder is not strictly sequential — larysa is the counter-example. She operates several rungs up (local file access, real PRs, ClickUp/Figma integrations) while missing the skills rung entirely, and her symptoms are exactly what the missing rung predicts: the agent "forgets," so she re-explains every session. This is diagnostically useful for the webinar — users can be technically advanced and architecturally stuck at the same time, and the fix is a rung they skipped rather than more capability.

Evidence

The full ladder, the "CLAUDE.md and skills — that's your maximum" ceiling, RAG-only-at-scale — 2026-07-14-yulia-interview.
Webinar title and non-programmer audience confirm the ladder as the webinar's spine — 2026-07-14-nina-interview.
Convergent structure (foundation docs + skills as the non-engineer's OS) — 2026-07-14-gap-between-ai-users-irreversible.
A high-rung user missing the skills rung, and the memory pain that results — 2026-07-21-larysa-interview.
Measured, team-level corroboration that the gap grows between rungs of mastery, not between license-holders and others: Stanford's 46-vs-46-team analysis shows the productivity gap between AI-mastering and lagging teams growing 4.8% → 19% (4×) over ~2.25 years — 2026-07-30-stanford-swepr-widening-gap. (Caveat: measures engineering teams, not this ladder's non-programmer audience; and the study asserts "quality of usage" as the differentiator without decomposing which rung supplies it.)

Concepts: personal-ai-operating-system, skills-as-memory, solve-first-then-skillify, harness (the engineer's continuation of the same ladder), evolution-of-agent-tooling, leave-less-room-for-imagination
Entities: eugene, yulia, allie-miller, larysa

Contradictions / Uncertainty

The rung ordering is Eugene's pedagogical framing, not an industry standard; other sources slice the progression differently (evolution-of-agent-tooling is tool-centric rather than user-centric). Status: tentative.
Larysa demonstrates the rungs are skippable, so the ladder is better read as a checklist of capabilities than as a strict sequence. Status: tentative.

Next Questions

Is the top rung the right ceiling? (Raised 2026-07-28 by lint.) This ladder's non-programmer ceiling is CLAUDE.md + skills, and thorsten-ball reaches the frontier with neither — no skills, no MCP, no slash commands, context in the codebase and AGENTS.md (2026-07-28-agentic-engineering-10x-developer). If his practice generalises, the ladder's top two rungs are a detour rather than a summit; if it doesn't, the reason is that he has a codebase to encode context into and this ladder's audience does not — which would be worth stating as the rung's precondition. See skills-as-memory for the three competing readings.
Does the final webinar script keep this exact rung order? (raw/notes/Webinar script.md — an authored deliverable, not an ingest candidate.)
Where do agents/processes (the harness's outer loops) sit for a non-programmer — above skills, or out of reach?

4.4 KiB Raw Permalink Blame History Unescape Escape