For generative skills I agree, but for me the real change is in how I read and debug code. After reading so much AI-generated code with subtle mistakes, I can spot errors much quicker even in human-written code. And when I can't, that usually means the code needs a refactor.

I'd compare it to gym work: some exercises work best until they don't, and then you switch to a less effective exercise to get you out of your plateau. Same with code and AI. If you're already good (because of years of hard won lessons), it can push you that extra bit.

But yeah, default to the better exercise and just code yourself, at least on the project's core.

▲

suddenlybananas 3 days ago | parent [-]

What do you mean you can spot errors much quicker?

▲

gobdovan 3 days ago | parent [-]

I mean that I've read so much AI generated code with subtle mistakes that my brain jumps straight to the likely failure point and I've noticed it generalizes. Even when I look at an OSS project I'm not super familiar with, I can usually spot the bugs faster then before. I'll edit my initial response for clarity.

▲

N2yhWNXQN3k9 3 days ago | parent [-]

> subtle mistakes that my brain jumps straight to the likely failure ... I can usually spot the bugs faster then before

doubt intensifies

	▲	3 days ago \| parent \| next [-]
		[deleted]
	▲	gobdovan 3 days ago \| parent \| prev [-]
		Doubt accepted. A spot-the-bug challenge on real OSS/prod code would be fun.