Chapter 11 / 20
11. People & Culture: Who Gets to Grow and Say No?
Provisional draft. These short chapters are not approved for publication. Original practitioner interviews, deeper reporting and author review remain outstanding.
A junior engineer hands over a working feature. The reviewer asks why a retry is safe after a timeout; the engineer can describe what the assistant wrote but not the behavior when the request is repeated. The problem is not that the engineer used AI. The problem is that the team has a correct-looking artifact without enough shared understanding to own it. This is an illustrative scenario, not a reported interview.
Anthropic's employee study reports that some staff gained reach into unfamiliar tasks and prototyped faster, while others worried about losing direct debugging practice or opportunities to ask colleagues questions. These are reports from a particular workplace, not longitudinal tests of skill. A junior–senior study examined AI-assisted debugging and how senior reviewers could use code and prompt histories to understand reasoning. It does not show a universal decline in junior capability. The evidence is enough to justify designing practice, not declaring a generation incapable.
Give people two kinds of support: a usable tool and a way to build judgment independent of it. Let a junior explain design alternatives and failure modes, pair on a small incident, and occasionally diagnose a bounded problem without AI. Let a senior spend review time on the "why" instead of only correcting the patch. Ask whether that time is actually in the plan or merely praised in speeches. Protect privacy when sharing prompt histories for coaching.
AI adoption should not become a loyalty test. Atlassian's 2026 survey commentary reports perceived pressure to demonstrate AI use; it does not reveal what any one employer's promotion committee actually rewarded. A manager can make the standard concrete by praising a well-verified use, a justified refusal on a sensitive task, and a reviewer who caught a dangerous assumption. Measure mentoring access and workload at team level; do not turn prompt counts into a ranking of people.
A question for the team: Ask someone early in their career to explain one change they own, including how it fails. Then ask a reviewer what feedback they gave about the reasoning. If the only feedback is "the code passed," invest in practice before using more generated output as a hiring or productivity argument.