Human Impact¶
The human side of working with AI agents — cognitive load, sustainable use, and team dynamics.
Pages¶
- The Addictive Flow State of Agent-Assisted Development — Dark flow, variable ratio reinforcement, and friction removal as mechanisms driving compulsive agent-assisted coding sessions
- Developer as CPU Scheduler: Attention Management with Parallel Agents — Treating developer attention as a schedulable resource when running multiple agent sessions in parallel
- Cognitive Load, AI Fatigue, and Sustainable Agent Use
- The Context Ceiling — AI agents hit a hard capability boundary on expert architecture work where context required exceeds what any window can hold
- Cross-Tool Translation: Learning from Multiple AI Assistants — Open standards and shared file formats make agentic patterns portable across 30+ AI coding tools
- Developer Control Strategies for AI Coding Agents — Empirical evidence that experienced developers plan, supervise, and validate agent output rather than vibe coding
- Initiatives and Community: Tracking the Agentic Engineering Landscape
- Safe Command Allowlisting: Reducing Approval Fatigue — Automatically approving low-risk operations reduces permission prompts so developers stay alert to the ones that matter
- PM on the AI Exponential: Short Sprints, Demos Over Docs, Simplicity — Four workflow shifts for product management when AI model capabilities improve exponentially
- Polya Small-Steps: Using AI to Think Better, Not Think Less — A problem-solving discipline that keeps AI as a thinking partner, working 1–2 steps at a time with comprehension as the exit gate
- Agentic Education: Persona Progression for Teaching AI Coding Tools — A four-persona scaffold (Guide, Collaborator, Peer, Launcher) for structured onboarding to agentic coding assistants, with independent-reconstruction checks that prevent self-efficacy gains from masking missing retention
- Deliberate AI-Assisted Learning: Accelerating Skill Acquisition — Interaction patterns that use AI as adaptive scaffolding within the Zone of Proximal Development, building skill rather than replacing it
- Skill Atrophy: When AI Reliance Erodes Developer Capability — Prolonged AI delegation erodes the independent problem-solving skills needed to review, debug, and architect code
- Strategy Over Code Generation — Empirical evidence from 150 data scientists shows strategy clarity predicts ML project success far more than AI coding speed
- Suggestion Gating: Why Fewer AI Completions Improve Developer Experience — Lightweight classifiers gate suggestions before display, improving acceptance rates 33–48% while cutting wasted inference
- AI Adoption Footprint: The Segmented Shape of Engineering Orgs — Engineering orgs adopt AI in three segments — power users, chat-tool middle, refusers — and the shape determines where enablement and tooling investment pays back
- Cohort Segmentation in the Copilot Usage Metrics API — The May 2026 Copilot API exposes four AI-adoption phases per user, a diagnostic primitive that recovers the segmented shape an aggregate utilization number hides
- LLM Refactoring Adoption Patterns — Five patterns for how developers modify ChatGPT refactoring suggestions — driven by prompt context completeness and refactor complexity
- Human-Facing Docs in the Agent Era: Mental Models Over Reference — When the audience reads alongside an agent, human docs shift from exhaustive reference to mental models, intent, and design exclusions — with the conditions under which the pivot backfires
- Programming Language Choice Still Shapes Agent Artefacts — Coding agents reach every language but the language you pick still decides performance ceiling, run cost, and verification effort — budget both
- Human-Equivalent Hours for Autonomous Coding Agent Productivity — Estimate the human engineering hours an autonomous agent's output would have taken so spend can be weighed against a denominator finance and headcount already use
- Intent-Centric Engineering: Oversight Over Authorship — When code generation is cheap, the engineer's leverage moves from authorship to specifying intent and governing humans-plus-agents-plus-tools — but only under specific conditions, with sharp failure modes (spec-as-code displacement, skill atrophy, vendor ToS gaps)
- AI Abundance Reshapes Software Engineering Identity — Long-form analysis of the builder/coder identity split: bottleneck migration, skill atrophy, and rigor relocation as code production is commoditized
- Evaluating Agent Patterns Catalog as a Source — Source assessment of agentpatternscatalog.org with citation guard-rails and an explicit no-MCP-wiring boundary
- From Preventive to Reactive: Front-Loading Security in AI Coding Prompts — AI assistants shift security thinking from writing-time to review-time; front-loading explicit security requirements in the initial prompt narrows that gap, under specific conditions
- Intervention Rate as a Diagnostic North Star, Not a Target — Treat the rate at which you correct an AI assistant as a segmented diagnostic signal, paired with quality and ambition metrics — not a single number to drive to zero
- Adapting AI Assistant Configuration to Developer Interaction Style — Cognitive diversity produces distinct Copilot interaction modes; per-developer persona configuration only pays back when team size and tool maturity offset the maintenance cost