> I can think of the tedious task of finding certain functionality within a codebase. I usually can't beat an AI agent harness at this task today.

Yup, I remember "racing" the AIs to figure things out in codebases just a year ago. Today, I have no chance. Whether it is due to degraded reasoning capabilities on my part or better models, I don't know.

▲

abustamam a day ago | parent | next [-]

At least in my case, much of the code in the codebase I'm working on is AI generated so even if I have an accurate mental model of how everything works, I have no idea where any of it is located or named.

▲

rasengan a day ago | parent [-]

To be fair, whenever I join a pre-existing code-base [1], it's the same. I have no idea and have to map it out ;)

[1] Not AI codebases (and of course, AI code bases I guess)

▲

markrages a day ago | parent [-]

I can't be the only one whose memory is so bad that I am like this in my own code base.

	▲	seekup a day ago \| parent \| next [-]
		I seem to remember - but cannot find, even with an AI boost - someone's "law of computing" or somesuch describing the amount of time that has to pass before code you wrote is indistinguishable to you from code written by someone else. At any rate the interval is not so long.
	▲	anon7725 a day ago \| parent \| prev \| next [-]
		In your own codebase you can at least run a "you simulator" to arrive at the answer fairly reliably. "Where would I have put this bit? Oh yes, of course ..."
	▲	pipes a day ago \| parent \| prev [-]
		You are not. :) my memory is disturbingly fried.

▲

kalstone a day ago | parent | prev | next [-]

AI is always going to be able to write a grep statement faster and more accurately than a human

	▲	block_dagger 19 hours ago \| parent [-]
		When AI is ready, it won’t need to grep at all. That is, it will train on the data in-situ instead.

▲

DonHopkins a day ago | parent | prev [-]

Now start thinking, if possible.

https://www.youtube.com/watch?v=43QHhEfzz-Q