The Code Review That Breaks You: How Performance Feedback Cycles in Engineering Recreate Childhood Wounds

WOMEN IN TECH • May 23, 2026

Last reviewed: June 2026 by Annie Wright, LMFT

It’s 9:14 on a Tuesday morning, and Kira is sitting in her home office with a cold cup of coffee she hasn’t touched. She’s a senior engineer, nine years into her career, the kind of person junior developers ask to review their trickiest pull requests. Fourteen comments have landed on her latest PR. Seven of them are from her senior colleague. Three are just question marks, hanging there with nothing else attached. She reads the first comment twice. Her chest tightens. Heat climbs from her collarbone to her jaw. She closes the laptop and sits with her hands flat on the desk, breathing shallow, waiting for something that isn’t happening technically to stop happening in her body.

Kira knows this feedback is routine. Her nervous system insists otherwise, and in this moment, her nervous system is the one running the show.

In my work with driven women in technical fields, I’ve watched this exact scene play out again and again, with different names, different companies, different stacks of code. The code review isn’t just a technical checkpoint for these women. It’s a charged interpersonal event that can reawaken childhood patterns of seeking approval or fearing criticism, and understanding that dynamic matters, not just for the individual woman closing her laptop with a racing heart, but for the engineering cultures that keep unintentionally reproducing the wound.

This piece walks through the clinical architecture of what I call code review anxiety in women engineers. We’ll look at how performance feedback cycles in engineering echo the attachment dynamics of childhood, why that produces a reaction that seems out of proportion to the event, and what actual healing looks like, in the body and in the org chart.

In short: Technical feedback anxiety is a nervous system response where code review comments activate the same threat circuitry as childhood experiences of conditional approval. It’s not a lack of confidence. It’s a body remembering something the mind has already filed away as old news.

Scene: Kira Opens the PR Comment Thread

Kira sits at her desk, the laptop’s glow catching the furrow in her brow. Fourteen comments on her pull request. The cursor blinks, waiting for her to read and respond. Seven comments come from her senior colleague, some terse, some cryptic. Three are just question marks, hanging there like silent judgments she has to somehow answer.

She reads the first comment twice. Her face flushes. Heat spreads from her chest up into her neck. Her breath quickens. She closes the laptop. She’s been coding for nearly a decade. She knows, intellectually, that this feedback is part of the job. Her body, though, is reacting as if something far more personal is at stake.

This moment is familiar to a lot of the women engineers I’ve worked with. The code review, a completely standard part of software development, becomes a source of outsized anxiety, and the anxiety isn’t really about the technical critique. The critique’s underlying meaning is where the charge lives.

For women whose sense of worth got shaped by early experiences where approval was conditional on intellectual performance, the code review functions as a proxy for a parent’s gaze. The reviewer becomes a stand-in for the authority figure who once scrutinized every effort, every test score, every school paper brought home for inspection. The pull request is the bid for approval. The comment thread is a nervous system event, reactivating something old.

This dynamic also intersects with the well-documented phenomenon of impostor syndrome, where women in tech carry persistent self-doubt despite evident competence. Both share a neurobiological infrastructure rooted in early attachment and social evaluation, an overlap I’ll return to later in this piece.

What Is Technical Feedback Anxiety?

The technical feedback isn’t just a professional checkpoint. It’s a relational event, charged with the echoes of childhood patterns. When your nervous system has been wired to respond to authority with heightened vigilance, even routine feedback triggers a full cascade of stress: a flush of heat, a tightening in the chest, trouble concentrating, an urge to either defend aggressively or withdraw. None of that’s weakness. It’s a nervous system interpreting the code review as a threat to relational safety, not a technical exchange between colleagues.

This same anxiety can feed the cycle of burnout in tech, where the constant need to prove oneself without much emotional support wears down even the most competent engineers. Recognizing technical feedback anxiety as a clinical phenomenon rooted in relational history opens the door to more compassionate interventions, whether that’s therapy, coaching, or a genuine shift in engineering culture.

For women in tech looking for more support here, the Women in Tech Resource Hub‘s got curated guidance on these dynamics, with both clinical insight and practical tools.

Why Does a Code Review Feel Like a Personal Threat?

For a lot of women engineers, receiving critical feedback during a code review does more than trigger a professional assessment. It activates a deeply ingrained neurobiological alarm system. This reaction isn’t about the code itself. It’s about the meaning attached to being evaluated and judged by an authority figure. The brain’s threat-detection circuitry has a hard time telling the difference between a technical critique and a fundamental challenge to a person’s adequacy.

Here’s what I keep coming back to when I explain this to clients. What researchers call social evaluation threat occurs when a person perceives that their performance or worth is being negatively evaluated by others, especially by someone in a position of authority. The brain processes this social threat using largely the same neural pathways that respond to physical danger, which produces a cortisol-driven fight, flight, or freeze reaction. That’s why a seemingly routine comment on a pull request can trigger a cascade of physiological stress responses. Racing heart. Flushed face. Tight chest. All of it out of proportion to what actually happened on the screen.

Trauma research documents this phenomenon well. Bessel van der Kolk, MD, author of The Body Keeps the Score, describes how the body archives relational injuries, the moments where someone in a position of care or authority caused harm, even unintentionally. For women whose childhood experiences included conditional approval or critical parenting, the code review can unconsciously replay these relational wounds. The reviewer becomes a stand-in for the parent. The PR becomes a bid for approval. The comment thread becomes a nervous system event that reactivates an old pattern, not a new problem.

I recently found myself rereading Brené Brown, PhD, LMSW, on shame and vulnerability, and it clarified something I’d been circling in session for years. Shame is closely linked to the fear of negative evaluation and rejection. When feedback feels shaming rather than constructive, it triggers a freeze or withdrawal response, no matter how technically sound the critique is.

Some women engineers experience what genuinely feels like a trauma response to code reviews, and this neurobiological framing helps explain why. Resilience and professionalism aren’t the issue. The nervous system got wired through early relational experience, long before anyone wrote a line of code, and that wiring is the whole story here, not a character flaw layered on top of it.

For women engineers who internalized the need to earn approval through intellectual performance, a code review can feel like a referendum on their value as a person, not just their code. That’s why even a neutral question mark, with nothing else attached, can trigger a reaction wildly out of scale to three characters on a screen.

Clinically, this lines up with what Martin Seligman, PhD, founder of positive psychology, documented in his early research on learned helplessness. When people experience repeated negative feedback that feels uncontrollable or unpredictable, they can develop a generalized helplessness response, expecting failure or rejection regardless of what they actually did. Over time, this creates a cycle where the anxiety about feedback undermines confidence and productivity, which then produces more of the very feedback the person feared in the first place.

For women living inside these dynamics, the challenge runs two layers deep: managing the technical demands of the job while regulating a nervous system that has decided feedback is a threat to survival. This is why “just get used to it” misses the point. It isn’t willpower. It’s a neurobiological pattern shaped decades before the first pull request.

How Does This Show Up in Women Engineers?

To see how this plays out in a real working life, consider Elena, a senior software engineer with fifteen years in the field. It’s late on a Thursday, and she’s spent three hours crafting a detailed response to a PR comment. The feedback she received was constructive but pointed, and she wanted to show she’d understood the concern and thoughtfully addressed it. Her response includes explanations, code adjustments, and links to the relevant documentation. It took her longer to write the response than it took to write the original change.

Her reviewer replies in thirty seconds flat. Four letters: “LGTM.” Looks good to me. The PR is approved and merged before she’s finished her tea.

Elena stares at the screen. There’s a strange emptiness where she expected relief. Instead there’s a quiet confusion. She isn’t sure what she feels. She’s sure it isn’t relief.

A subtle but clinically important piece of code review anxiety lives inside this small vignette. The approval Elena received was transactional, an efficient sign-off confirming the code met technical standards. What it lacked was relational recognition: acknowledgment of the effort she’d invested, the competence she’d shown, the person behind the diff.

For women engineers whose nervous systems are wired to seek relational validation, this kind of feedback can feel like being seen but not truly seen. The “LGTM” closes the loop on the technical process and leaves the emotional loop wide open, waiting for a connection that was never on offer in the first place.

The performance-approval merger a lot of women carry from childhood, where love and acceptance were conditional on achievement, connects deeply to this dynamic. The professional environment replicates the old pattern, replaying the same script: prove your worth to be accepted. When feedback doesn’t meet the need for relational attunement, it can feel like rejection, even when the code itself gets a clean approval.

Code review anxiety and impostor syndrome share the same infrastructure for this reason: a basic uncertainty about belonging and competence, fueled by early relational wounds and reinforced in adult professional settings. See our piece on impostor syndrome and code review anxiety for more on this overlap.

The constant stress of these feedback loops can also feed straight into burnout, draining resources that don’t refill overnight. Our burnout guide for women in tech explores how that stress compounds over months and years.

Recognizing that your reaction to code review comments isn’t a personal failing but a signal from your nervous system can be genuinely freeing. It invites feedback to become a tool for learning instead of a trigger for survival mode. For women engineers, that shift is a step toward healing an old wound that keeps getting replayed in every PR thread.

Where Do Performance and Approval Get Fused in Childhood?

For a lot of women engineers, the emotional charge of a code review isn’t only about the feedback in front of them. It’s rooted in a developmental history where performance and approval were never separate things to begin with. I’ve come to think of this as the performance-approval merger, and it originates in childhood environments where love and acceptance were conditional on meeting a high standard of intellectual or behavioral achievement.

Think of a household where a child’s worth got measured by grades, or success in whatever extracurricular mattered most to the parents. The parents might have been genuinely loving while still communicating affection mostly through critique. “I’m proud of you when you get an A.” “You’re smart, but you could do better.” In a home like that, failure feels unsafe, and the child learns early that approval is earned, never simply given.

A nervous system finely tuned to detect evaluation from anyone in authority grows out of that developmental pattern, activating fight, flight, or freeze long before the child has words for what’s happening. Fast forward twenty years, and the code review replicates the exact shape of that old dynamic: the reviewer stands in for the parent, the pull request becomes the bid for approval, and the comment thread triggers an attachment wound that has nothing to do with software.

Women engineers so often report a disproportionate physiological and emotional reaction to code review comments for this reason, even when they know, intellectually, that the feedback is normal and necessary. The comments aren’t just technical. They’re relational echoes of a time when approval was scarce and always conditional on something.

Academic environments that mirrored the same dynamic often account for this history: schools that emphasized grades over learning, parents who monitored homework with a critical eye rather than a curious one. Both reinforce the same message, performance equals worth, and engineering culture’s emphasis on correctness and measurable output can unwittingly reactivate the pattern without anyone involved intending harm.

Code review anxiety isn’t a matter of “professional resilience” or “technical competence.” It’s a nervous system survival mechanism, wired in childhood, now replayed at a standing desk in front of a monitor. That insight opens the door to a more compassionate approach, for the individual woman and for the team around her.

Both/And: The Code Review Is a Normal Engineering Process AND It Carries the Weight of Something Older

Here’s the truth I want you to leave this section holding. The code review is a standard, necessary part of engineering work, AND for a lot of women engineers, the nervous system response to it carries the weight of something considerably older and more vulnerable.

Six months into therapy, Kira sits with her therapist, turning over a recent code review that left her unsettled for the rest of the day. Her therapist asks a simple question. “Who does the reviewer remind you of?”

Kira hesitates. The question stirs something below the surface, a memory she hadn’t consciously connected to a work event at all. After a pause: “My father. He used to read every school paper I wrote and always found what was missing.”

Her therapist follows the thread. “And was your father usually wrong?”

“No,” Kira says quietly.

There’s a long silence. The room holds the tension between the technical feedback and the emotional resonance underneath it. Kira’s nervous system was never responding to the code. It was responding to the echo of a childhood attachment figure whose approval felt both essential and permanently out of reach.

That’s the core clinical insight sitting inside this whole piece. The code review’s a technical event. The response to it’s relational. A reviewer’s comments get interpreted by the nervous system as a test of worthiness, not merely a check on code quality. An “LGTM” that closes a review thread may be technically sufficient and still land as emotionally insufficient, because the nervous system was never asking for a sign-off. It was asking for recognition, of effort, of competence, of the fact that a person, not just a diff, was on the other end of the thread.

Naming this both/and gives women engineers real agency in their feedback relationships. It lets them hold the technical and the emotional at the same time, without collapsing one into the other and without dismissing their own lived experience as an overreaction.

In practice, this looks like building a somatic awareness of the feedback-anxiety cycle and learning to tell the technical critique apart from the emotional charge riding alongside it. Therapy can help unpack the childhood piece, offering a corrective relational experience that can genuinely rewire old attachment patterns over time. Executive coaching, meanwhile, can build the skills to integrate feedback without triggering the survival response in the first place, which builds a healthier working relationship with one’s own output.

Of course this is hard to hold at once. You didn’t build the pattern on purpose, and unwinding it takes longer than reading a definition box. That’s not a failure of insight. That’s just how nervous systems change.

For women in this terrain, resources like therapy for women in tech and executive coaching for women in tech offer support tailored to exactly this interplay of identity, nervous system regulation, and professional development.

Code review anxiety isn’t a personal failing. It’s a signpost pointing toward an early relational wound and the ongoing challenge of working inside environments that unconsciously replay it. Naming the architecture is what creates room for healing, for resilience, and for a more sustainable career in engineering over the long run.

For more on how this intersects with impostor syndrome, see Impostor Syndrome and Women in Tech. For the burnout risks tied to this exact feedback cycle, see Burnout for Women in Tech.

The Systemic Lens: Why Does Code Review Culture Hit Women Differently?

The anxiety women engineers carry around code reviews doesn’t come out of nowhere. It’s embedded in a larger system where gender bias, power imbalance, and cultural norms shape how feedback gets given and interpreted before a single line of code enters the conversation. This isn’t your unique failing. This is a pattern with a structural origin.

Multiple studies have documented that women’s code submissions face higher scrutiny and lower acceptance rates than men’s, particularly in open-source projects. It’s a pervasive culture where women’s work gets held to a different standard, with a higher volume of comments and a less encouraging tone compounding the toll of every review cycle.

A broader social dynamic outside of tech mirrors this pattern. Linda Babcock, PhD, economist and researcher on gender and negotiation, has documented how women who initiate negotiations get penalized more harshly than men, not for lack of competence, but because of social costs imposed by gendered expectations. In engineering teams, women who push back on a comment risk getting labeled “difficult,” discouraging the very engagement a good code review is supposed to invite.

Code review culture, with its emphasis on rapid iteration and blunt critique, often fails to account for the relational context in which feedback lands. Women engineers end up managing the technical demands of the job plus the emotional labor of tracking how their competence gets perceived inside a male-dominated environment, labor that can activate the same nervous system responses tied to early attachment wounds.

The mechanism runs deeper than any one team’s culture. The systemic undervaluing of women’s contributions in engineering feeds directly into what Seligman’s framework calls learned helplessness: efforts to improve get met with disproportionate resistance. Repeated negative feedback cycles don’t just trigger anxiety, they erode motivation over time.

The systemic lens also shows how tech’s cultural obsession with “resilience” quietly masks structural inequity. Women who struggle with feedback anxiety sometimes get judged as lacking grit, rather than recognized as responding to a feedback environment that is, for them, a reactivation of early relational trauma. That misreading isolates women further and reinforces the story that the distress is a personal failing, not a signal about the environment itself.

The consequences of this pattern aren’t small. It contributes to the attrition of talented women engineers, perpetuates the gender gap in technical leadership, and undermines psychological safety across whole teams, organizing identity around hyper-vigilance meant to preempt criticism before it lands, which leads, eventually, to exhaustion.

Here’s how the inheritance lives in a Tuesday afternoon. It’s the PR sitting open in a browser tab for twenty extra minutes before Kira can bring herself to submit it. It’s Elena rereading her own comment three times before posting, softening a technical disagreement into something that won’t read as “difficult.” It’s the body that tenses at the sound of a Slack notification an hour after a review request went out, because the body’s learned that silence, too, can be a verdict.

This systemic lens reframes code review anxiety as a cultural pattern, not individual fragility, one that demands change from team norms up through broader social attitudes about gender and performance.

What Does Healing Actually Look Like?

Healing from the cycle of technical feedback anxiety takes a layered approach, one that addresses both the nervous system’s conditioned response and the relational patterns rooted in childhood. Here’s the framework I use with women engineers who want to disentangle the emotional charge from the technical feedback itself.

1. Somatic regulation: reclaiming nervous system safety. The disproportionate physiological response to a code review signals that the nervous system perceives threat where there’s none, or none proportionate to the actual event. Grounding exercises, breath awareness, and body scanning can shift the nervous system out of fight, flight, or freeze and into safety. When opening a PR thread triggers heat in the face or tightness in the chest, pausing to notice the sensation without judgment creates a window of tolerance. Modalities like Sensorimotor Psychotherapy, developed by Pat Ogden, PhD, along with Somatic Experiencing, tend to be especially effective here, helping women tell present-moment reality apart from past relational wounds.

2. Separating technical feedback from emotional charge. One of the most useful interventions is helping a client separate the content of a code review from the emotional narrative layered on top of it. “Needs refactoring” is a technical request, not a judgment of personal worth, even when it lands like one. Replacing “my reviewer thinks I’m incompetent” with “the reviewer wants to improve the code” recalibrates the appraisal before the body spirals.

3. Therapy for the childhood piece. Because the code review so often reactivates an attachment wound, therapy that explores a client’s developmental history can change the whole shape of the pattern. Approaches like attachment-based therapy, Internal Family Systems, developed by Richard Schwartz, PhD, or relational psychotherapy give a woman a container to explore an internalized critical voice and an unmet need for approval that predates her career by decades. Over time, this work can rewrite the old narrative equating approval with survival.

4. Building a new feedback relationship with your work. Healing means building a relationship with feedback that isn’t organized around fear. That might mean setting boundaries around when to review comments, building small rituals that honor effort regardless of outcome, or finding peer networks that offer empathic reflection instead of judgment. Communities of women engineers who talk openly about feedback anxiety reduce isolation and normalize the emotional complexity of technical critique.

5. Advocating for systemic change. Individual healing has to be paired with advocacy for systemic change. Women engineers and their allies can reshape code review culture by promoting psychological safety and naming the documented gender bias already baked into review processes. Organizational leaders can run training on unconscious bias in code review and recognize the emotional labor women invest in facing these dynamics every week.

You’re not broken, and you’re not imagining how hard this is. A nervous system that learned, decades ago, that approval was scarce and performance-contingent is going to keep reacting to feedback as if the stakes are existential, until something in the pattern gets addressed directly. That isn’t a character flaw. That’s biology doing exactly what it was trained to do.

Kira still closes her laptop sometimes, hands flat on the desk, coffee going cold beside her. That hasn’t disappeared, and it may never fully disappear. What’s changed is what happens next. She knows, now, whose gaze she’s actually flinching from, and that knowing gives her somewhere to put the flinch besides her own self-doubt. If you’re a woman in engineering living inside the emotional terrain of code reviews, know this: your experience is a meaningful signal, not a personal flaw. Healing happens when we honor the full complexity of the response, integrate the technical with the relational, and build teams and cultures that recognize the person behind the code. You’re not alone in this, and you’re not the only one whose chest tightens at a notification that says nothing more than “3 new comments.”

Warmly, Annie.

Related Reading and Clinical References

Bessel van der Kolk, MD. The Body Keeps the Score: Brain, Mind, and Body in the Healing of Trauma. New York: Viking, 2014.

van der Kolk BA, Wang JB, Yehuda R, Bedrosian L, Coker AR, Harrison C, et al. “Effects of MDMA-Assisted Therapy for PTSD on Self-Experience.” PLoS One 19, no. 1 (2024): e0295926. doi:10.1371/journal.pone.0295926. PMID: 38198456.

Brown, Brené. Daring Greatly: How the Courage to Be Vulnerable Transforms the Way We Live, Love, Parent, and Lead. New York: Gotham Books, 2012.

hooks, bell. All About Love: New Visions. New York: William Morrow, 2000.

Seligman, Martin E. P. Helplessness: On Depression, Development, and Death. San Francisco: W.H. Freeman, 1975.

Medical Disclaimer