AITA for telling my coworker his “self-taught background is showing” when he kept pretending to understand coding concepts?

A team meeting took a wild turn when one programmer’s terrible code left jaws on the floor. A 28-year-old female developer, sharp and self-taught, found herself stuck cleaning up her 31-year-old coworker’s mess. What pushed her over the edge? His smug “I know that” attitude, despite his work screaming otherwise.

This isn’t just a tale of bad code—it’s a showdown of egos and workplace grit. Was she too harsh in calling him out? The online community dove in with fiery takes, from cheers to critiques. Buckle up for a story that’ll make you rethink how we navigate tension at work!

‘AITA for telling my coworker his “self-taught background is showing” when he kept pretending to understand coding concepts?’

It all started in a team meeting when OP, a 28-year-old female programmer, watched her 31-year-old male coworker boast about being self-taught—then unveil code so bad it was almost comical:

Finally, OP’s patience snapped. She called out his pretense, pointing out that his attitude was dragging the whole team down:

This story captures a classic workplace clash: skill gaps meet stubborn pride. The coworker’s shoddy code is bad enough, but his refusal to own his mistakes—hiding behind a smug “I know that”—is what really grinds gears and slows the team down. His behavior screams insecurity, and it’s creating extra work for everyone.

Workplace expert Dr. Amy Gallo, in her HBR Guide to Dealing with Conflict, puts it perfectly: “When people dodge feedback or refuse to admit errors, they stall their own growth and sabotage the team.” That’s exactly what’s happening here—the coworker’s defensiveness is blocking progress.

OP’s frustration makes total sense, but tying his bad code to his “self-taught” status might’ve hit a nerve unnecessarily. Since she’s self-taught too, it could’ve come off as a personal dig. A smoother approach, like zeroing in on specific coding flaws, might’ve kept things less heated.

Some community members flagged gender dynamics, hinting the coworker might chafe at being coached by a woman. It’s a real issue in tech, where women often face pushback in technical roles. Still, that doesn’t excuse his lack of humility or teamwork.

OP should keep giving clear, focused feedback—like pointing out ways to streamline code—while nudging her boss to rethink task assignments so she’s not always playing cleanup crew. The coworker, meanwhile, needs to drop the ego, soak up feedback, and level up his skills.

This dust-up shows how much teams rely on honesty and a willingness to grow. Without that, even the best coders can’t save the day.

Check out how the community responded:

The online community went all in on OP’s story, serving up a lively mix of support, advice, and laughs. Here’s the full scoop:

Plenty of users backed OP, saying her coworker’s know-it-all act begged for a reality check:

Some zeroed in on possible gender dynamics, hinting the coworker’s attitude might stem from discomfort with OP’s expertise as a woman:

Others agreed with OP’s point but suggested her clapback could’ve been more tactful:

A few brought humor to the table, poking fun at the coworker’s attitude while siding with OP:

Some questioned how the coworker even landed his job with such weak skills:

Others offered balanced takes, critiquing both sides while leaning toward OP:

OP’s run-in with her coworker exposes how ego can derail teamwork when skills don’t match the hype. Her irritation with his fake confidence strikes a chord, and the community’s blend of support, advice, and humor shows just how messy these conflicts can get.

While OP’s point landed, her delivery sparked debate about finesse. This story screams the value of humility and collaboration in any workplace. How would you deal with a coworker like this? Share your take below!