Open to new projects — Angular, TypeScript, Node.js, AI Get in touch →
← Back to blog

AI Took the Creative Part of the Job. No Wonder Work Feels Empty.

AI does the creating, we do the checking. Why so many jobs feel less satisfying lately, and how to win back the part of work that made it fun.

You finish the day. Tickets closed, PRs merged, everything green. And you feel… nothing.

No “I built that” moment. No small pride. Just a long list of things you approved, adjusted and pasted. If that sounds familiar, you’re not lazy and you’re not burned out in the usual way. You lost the part of the job that used to fill you up.

The fun part was the hard part

Think about why you liked your job in the first place. For most developers it wasn’t typing. It was the puzzle. Staring at a problem, trying something, failing, and then — finally — seeing it click.

That struggle was the reward. And it’s exactly the part AI now does first.

The same thing is happening everywhere, not just in code. Designers get ten AI mockups and pick one. Writers edit drafts they didn’t write. Marketers tweak generated copy. Analysts check AI summaries. The job title stayed the same. The job moved from making to checking.

A day as a maker
Think about the problem
Sketch an approach
Struggle, get stuck
Find the solution
→ "I built that"
A day as a checker
Write a prompt
Read the output
Fix what's almost right
Approve, move on
→ "I reviewed that"

Both days can be productive. Only one of them feels like yours.

Why checking feels so empty

Psychology has a good explanation for this. Self-determination theory says we feel motivated when three needs are met: autonomy (I choose how), competence (I’m getting better), and relatedness (it matters to people). Creative work hits all three. Reviewing generated work mostly hits none.

There’s also the IKEA effect. In a well-known set of studies, people valued things they built themselves — furniture, origami, Lego — much more than identical things they didn’t build. Effort creates attachment. Remove the effort, and the attachment goes with it.

And now there’s direct evidence for AI too. A 2025 study with thousands of participants found that people using generative AI produced better work. But when they then switched to tasks on their own, their motivation dropped by about 11% and boredom went up by about 20%.

The core idea: Satisfaction doesn't come from output. It comes from the struggle that produced it. When AI removes the struggle, it quietly removes the reward too.

It’s like a cache that’s always warm. Every answer comes back instantly — and you never learn where the data actually lives. Fast, efficient, and a little hollow.

Where are you on the spectrum?

Not every task needs your creativity. The problem is when all of your tasks slide to the right side of this scale.

Creator
You shape the idea
Collaborator
You and AI shape it together
Operator
You approve what AI made

A healthy week has some of each. A week spent only as an operator is efficient — and it slowly drains you.

How to get the creative part back

You don’t need to quit AI. You need to choose where you let it lead.

Do the thinking first, then ask AI. Before you prompt, spend ten minutes sketching your own approach. On paper, in a comment, anywhere. Then compare it with what AI suggests. Now you’re a designer with an assistant, not a reviewer with a queue.

Keep one “hand-made” problem per week. Pick one interesting piece of work — a tricky bug, an algorithm, a UI interaction — and solve it yourself. Treat it like a protected meeting. It’s your weekly dose of “I built that”.

Let AI take the boring, not the interesting. Boilerplate, migrations, test data, docs: hand them over happily. Architecture, naming, the core logic: keep those close. Delegate the chores, not the craft.

Build something useless on the side. A side project with no deadline and no AI is a great reset. It reminds your brain what creating feels like when nobody is measuring output.

Weekly creativity check
I solved at least one problem without AI
I sketched my own approach before prompting
I made a decision AI couldn't have made for me
I can point at one thing and say "I built that"

If you can’t tick any of these, the emptiness you feel isn’t a mystery. It’s a missing input.

This isn’t nostalgia

I use AI every day, and I don’t want to go back. It removes a lot of tedious work, and that’s genuinely good.

But “faster” and “more satisfying” are not the same thing. Companies will optimise for the first one. Protecting the second one is on you.

Try this today: Pick the next interesting task on your list. Before opening any AI tool, write down how you would solve it — five lines is enough. Then build it, with or without help. Notice how different the finish feels.

Sources: