In the AI era, traditional productivity proxies like lines of code are failing. A better measure is a team's ability to complete high-quality "at-bats": the full cycle from idea generation to building, feedback, and validation. This metric captures execution efficiency, team culture, and the ability to learn quickly.

Focusing on individual performance metrics can be counterproductive. As seen in the "super chicken" experiment, top individual performers often succeed by suppressing others. This lowers team collaboration and harms long-term group output, which can be up to 160% more productive than a group of siloed high-achievers.

Psychologist Cat Hicks' research revealed that many developers, including highly experienced ones, suffer from "code review anxiety." This intense fear of judgment prevents them from engaging in a process critical for learning and quality control, and they often suffer in silence, afraid to speak up about it.

The speaker observed a pattern at Meta where leadership sets ambitious, often unrealistic deadlines. When these are consistently missed without consequence, the pressure becomes artificial. This erodes motivation, causing engineers to disengage and treat the deadlines as noise rather than serious goals.

AI coding assistants can make engineers so hyper-productive that they mistakenly believe they can handle the entire product lifecycle alone. This leads them to ignore critical inputs like design, customer briefs, and collaboration, resulting in technically functional but ultimately useless products.

While celebrated for high output, 'cracked engineers' can be a double-edged sword. Their focus on speed can create a 'trail of bugs' and technical debt that burdens the team. This superstar culture also risks overlooking essential 'glue work' and may reward individuals who take credit for team efforts, creating an antisocial environment.

Measuring engineering success with metrics like velocity and deployment frequency (DORA) incentivizes shipping code quickly, not creating customer value. This focus on output can actively discourage the deep product thinking required for true innovation.

Similar to technical debt, "narrative debt" accrues when teams celebrate speed and output while neglecting shared understanding. This gap registers as momentum, not risk, making the system fragile while metrics still look healthy.

The "brains in jars" mental model treats developers as isolated, interchangeable units, ignoring collaboration and social dynamics. This simplistic view leads to burnout, low productivity, and an inability to solve complex problems because it devalues essential work like mentoring and learning out loud.