Priya (Composite Developer)
Priya is not a single individual but a trajectory, a developmental pattern recurring across the technology industry with increasing frequency since 2025: an intelligent, motivated early-career professional who enters the workforce already fluent in AI-assisted development, produces impressive immediate output by every metric organizations track, and discovers, during a crisis requiring independent diagnostic reasoning, that eighteen months of high performance built no architecture for handling what the AI cannot. Her story is Bjork's framework made concrete—the performance-learning dissociation, the generation effect's absence, the spacing eliminated by massed AI-assisted work, the interleaving bypassed by type-specific solutions, and the metacognitive confidence (based on fluent code review) that predicted nothing about diagnostic capability (based on storage strength she never built).
In the AI Story
Priya's workflow—describe bug to Claude, receive diagnosis, apply fix, move on—eliminates all four canonical desirable difficulties. No generation: she receives solutions rather than producing them. No spacing: each bug is resolved in a single massed interaction with no overnight gaps for consolidation. No interleaving: each solution is type-specific, eliminating the discrimination challenge that mixed problem types would require. No contextual variation: every interaction occurs in the same interface, under the same conditions, producing knowledge that does not transfer to the novel configurations that production failures present.
Her eighteen-month trajectory produced a specific cognitive profile that the New Theory of Disuse predicts: high retrieval strength (maintained externally by Claude's permanent availability) and low storage strength (because the conditions for building it—effortful retrieval after forgetting—never occurred). The profile is invisible to every evaluation system her organization uses: velocity metrics (high), defect rates (low), code quality (good), manager assessments (positive). The gap appears only when tested by the 2 a.m. production failure—a novel, ambiguous, proprietary-component problem that Claude's training data does not contain and that her own storage strength, never built, cannot address.
The senior engineer who diagnoses the race condition in forty-five minutes possesses exactly what Priya lacks: storage strength built through years of formative difficulty. Her advantage is not 'more experience' but a specific cognitive architecture—internal representations of system behavior, pattern libraries of failure modes, discriminative skill for categorizing ambiguous symptoms—that can only be constructed through the generation, spacing, and interleaving that Priya's AI-first workflow eliminated. The architecture took a decade to build and cannot be retroactively installed by switching workflows at month nineteen.
Priya's case raises the developmental window question that Bjork's framework makes urgent. Cognitive development is sequential: the knowledge built at month three becomes the scaffolding for month six's knowledge. When early deposits are not made—because AI handled the work that would have produced them—later deposits have no scaffolding to attach to. The architecture is not merely delayed; it is structurally different from the architecture that would have developed under formative conditions. The eighteen months were not merely slower learning; they were a different developmental trajectory whose endpoint is a different kind of practitioner—one optimized for AI-augmented execution and underdeveloped for independent reasoning.
Origin
The composite is drawn from patterns Bjork observed across multiple organizations and from the developer trajectory that Edo Segal documented in The Orange Pill—the engineer who could ship code at twenty-times velocity with Claude but who had not built, during the acceleration, the diagnostic intuition that years of manual debugging deposit. Bjork's simulation made the developmental mechanism explicit: the velocity came from external retrieval strength; the missing diagnostic capability came from absent storage strength; and the gap between the two is the precise prediction of a theory whose experimental support is measured in thousands of replications.
Key Ideas
High performance, low capability. Priya's eighteen months produced excellent output by every immediate measure (velocity, code quality, defect rates) while building minimal diagnostic capability—the dissociation between performance and learning made concrete in a single career arc.
Missed formative windows are not recoverable. The diagnostic architecture that manual debugging would have built during Priya's first eighteen months cannot be retroactively installed—cognitive development is sequential, and missed early deposits leave later knowledge without scaffolding.
Evaluation systems are blind to the gap. Every metric Priya's organization uses (output-focused, immediate, quarterly) rewards her trajectory, because the gap between retrieval strength (high, externally maintained) and storage strength (low, never built) is invisible to systems measuring performance rather than architecture.
Crisis reveals what metrics conceal. The 2 a.m. production failure is the delayed test that reveals storage strength—and that organizational evaluation systems, optimizing for quarterly output, systematically fail to administer until the cost of the gap is already catastrophic.
Appears in the Orange Pill Cycle
Further reading
- Bjork, Robert A., and Elizabeth Ligon Bjork. 'A New Theory of Disuse and an Old Theory of Stimulus Fluctuation.' From Learning Processes to Cognitive Processes, vol. 2, Erlbaum, 1992.
- Soderstrom, Nicholas C., and Robert A. Bjork. 'Learning Versus Performance.' Perspectives on Psychological Science, vol. 10, 2015, pp. 176–99.