<- all tokdocs

Grieving the Coding Job AI Changed: A Senior Engineer Explains

By , founder of Mavric and Apso

View on TikTok ->

Many software engineers feel uneasy about AI coding tools even when the tools work well for them. A senior engineer on TikTok gives that feeling a name: grief for the part of the job AI removed, the puzzle of finding and fixing broken code. She argues that the grief and her gratitude for the tools can both be true.

The video comes from Rachel, who posts as @buildinghappi. It is a short monologue to camera with no code or screen recordings. Her caption sums up the thesis: she still gets satisfaction from building with AI, but it hits different when it is home grown.

Why do software engineers feel grief about AI?

Rachel's answer starts with why she became an engineer. She did not know what she wanted to be in college. She took one computer science class and fell in love with the puzzle. Coding felt like an art to her more than a science, and she was surprisingly good at it.

She describes staying up all night on broken code, reading Stack Overflow answers and documentation for hours. Then she would find the misspelled variable, the one character out of place that broke everything. The four hours of reading stopped mattering the moment the code worked.

Her line about that cycle is the core of the video: "The frustration and the satisfaction were somehow the same feeling and it was addicting."

The reward felt earned. That is the thing she says she lost. When an AI tool writes the code and finds the bug, the frustration goes away, and the satisfaction that came with it goes too.

The climb to senior engineer

Rachel chased that feeling through years of imposter syndrome. She doubted she was technical enough or smart enough, and she doubted she belonged. She says she put more blood, sweat and tears into becoming a senior software engineer than she would like to admit.

She frames the senior title as a mountain she spent her life climbing. The view from the top was supposed to be the payoff.

"A picture of the thing, not the thing"

The turn in the video comes when she reaches the top. In her metaphor, she finds a green screen where the view should be: "Everything I climbed towards was a picture of the thing, not the thing."

She no longer chases the bug. She describes what she wants and watches something else build it. The struggle she loved got automated while she was busy earning the right to do it.

The metaphor separates two things. One is the job title, which she still holds. The other is the daily activity that made the title worth having, and that is what changed.

Is this an anti-AI argument?

Rachel says it is not, and she is careful about this. She says she loves that more people now get access to building software. She says we are not going back, and that the change to the job may be good and may be inevitable.

Her conclusion is about naming the emotion: "It was never about the AI. It's that I'm grieving a job that I'm not really allowed to say I lost."

She is still employed. What she lost is the texture of the work. She points out that there is no accepted way to mourn that while the industry celebrates the tools that changed it.

Why the feeling is hard to talk about

Rachel's title and job are both still there, which is why she says she is not allowed to call it a loss. Her video argues that the daily activity can be the thing that mattered. In her account, being glad that more people can build software does not cancel missing four hours on a bug that turned out to be one character.

The format matches the message

The whole video is one continuous selfie-style shot of Rachel at her desk holding a small handheld mic. Word-by-word captions follow the audio. There is no b-roll and no code on screen. The last frame shows her leaning out of view and leaving an empty desk chair.

The plain setup fits what she is doing, which is working through a feeling out loud instead of pitching a hot take about AI.

Bottom line

The unease many engineers feel about AI coding tools can be grief for the lost work of debugging and problem solving, separate from what they think of the tools. Rachel's case is that the reward loop she loved was addictive because it was earned. Reaching a senior title just as that work changed left her with the title and without the activity it stood for. She welcomes wider access to software building and still mourns the version of the job she trained for.

Sources

  • Stack Overflow - where she describes spending hours reading to fix broken code

Published June 25, 2026. Based on a TikTok by @buildinghappi. Full video notes (markdown)