Imposter syndrome when taking AI help – Why?

Somewhere in the middle of a good Cursor week, a rude little voice shows up.

It says: if an agent wrote half of that, do you still count?

That voice is lying. It is also very good at its job.

What the spiral actually is

Imposter syndrome, classic cut: “I’m about to be found out.”

AI-flavored remix: “I’m only competent because of the autocomplete.” Or “real engineers don’t need a roster.” Or “hiring managers will smell the agents on me.”

Meanwhile I’m the one who designed the jobs, wrote the gates, refused unsupervised push, made the agents upsert into SQLite instead of vibing a spreadsheet, and sat there reading diffs until I could explain them. That is not a spectator sport.

I already wrote the security half of this on the bench: real security vs security theater. Humans own the dangerous verbs. Assistance is not abdication. Imposter brain wants to pretend those are the same sentence.

What I did not outsource

Taste. Priority. “Is this the right thin slice?” “Does this belong on the Organon bench?” “Will I defend this in an interview at 9am?”

Agents draft. Agents research. Agents update the ledger. They do not get to decide that a job application ships, that a dependency bump is fine, or that “it compiles” means “it’s done.”

If I cannot explain the change, it does not ship. That rule is older than the current model parade. The models just made it louder.

Why I shouldn’t wear the costume

Because the alternative fantasy is worse: pretend I never use AI, then either fall behind or lie.

Because every senior engineer I respect already uses force multipliers – compilers, linters, Stack Overflow, junior teammates, search. Agents are a louder multiplier. The craft is still judgment under constraint.

Because “I built a semi-automated job search tracker so my feelings can’t gaslight my productivity” is not the resume line of someone who checked out. It’s the resume line of someone who builds instruments when the process hurts.

Because job design for agents is engineering. Prompt mush is not. I care which one I’m doing.

The practical deal with myself

When the voice shows up, I ask three questions:

1. Did I understand the change before it left the building?
2. Did I choose the job, the non-goals, and the blast radius?
3. Would I still defend this work if the model vendor vanished tomorrow?

If yes, the voice can go sit in the hallway. If no, that isn’t imposter syndrome. That’s a real process bug. Fix the bug.

I’m allowed to be fast and still be the author of record. Instruments, not vibes. Including the instrument between my ears that keeps trying to call me a fraud for using tools well.

~ Trish