These articles are 25 years old.

Sadly, I've seen multiple well-known developers here on HN argue that reading code in fact isn't hard and that it's easy to review AI-generated code. I think fundamentally what AI-generated code is doing is exposing the cracks in many, many engineers across the board that either don't care about code quality or are completely unable to step back and evaluate their own process to see if what they're doing is good or not. If it works it works and there's no need to understand why or how.

▲

g_sch 2 days ago | parent | next [-]

I think this is equally true of writing. Once you see something written one way, it's very hard to imagine other ways of writing the same thing. The influence of anchoring bias is quite strong.

A strong editor is able to overcome this anchoring bias, imagine alternative approaches to the same problem, and evaluate them against each other. This is not easy and requires experience and practice. I am starting to think that a lot of people who "co-write" with ChatGPT are seriously overestimating their own editing skills.

▲

Zanfa 2 days ago | parent | prev [-]

Reviewing code is basically applying the Chesterton’s fence principle to everything. With AI code there’s typically so much incidental noise that trying to identify intention is a challenge.

But then again I’ve found a lot of people are not bothered by overly convoluted code that is the equivalent of using a hammer for screws either…

	▲	lazide 2 days ago \| parent [-]
		Worse - there is no actual intention, so attempting to grok it from the code is even more wasted energy. You have to nitpick everything, because there is no actual meaningful aim that is consistent. I ran across an outsourcer that did the same thing about 20 years ago (near as I could tell he was randomly cutting and pasting random parts of stack overflow answers until it compiled!). We got him away from the code base/fired ASAP because he was an active threat to everyone.