You and the AI agree, but how about you and the team who will eventually read and do code review.

Cognitive burden increases marginally with AI assisted coding.

This is why we haven't seen big projects(think browsers and browser engines) spawning in the past year.

trhaynes an hour ago | parent | next [-]

Indeed. I'm curious what the security team has to say about that approach, for example.

	▲	brabel an hour ago \| parent [-]
		If you get an AI to review the code especially for security, it does a very good job st finding issues. Better than any human reviewers I have worked with, and getting better. As someone who works in security , I feel much less worried about security bugs on code reviewed by a AI for security issues, be it written by AI or human.

▲

zdragnar an hour ago | parent | prev | next [-]

It's anthropic, of course the entire team is also using AI to do the code reviews.

▲

a2ff6eeb0 an hour ago | parent | prev [-]

> but how about you and the team who will eventually read and do code review.

Why are you reviewing AI code in detail? Do you also review the assembly output of GCC line by line?

▲

electric_toucan 44 minutes ago | parent | next [-]

Compilers like GCC are deterministic and the source code already fully defines the behavior. LLMs are non-deterministic and will accept ambiguity, filling in details where you haven’t. These sorts of comparisons aren’t really fair.

In the case of writing, it’s like hiring someone to write a book for you vs. hiring someone to translate a book you wrote into another language. In the first case, you didn’t really define the message for readers, whereas in the second case you did, and the translator is converting that same message for another audience to consume.

	▲	a2ff6eeb0 17 minutes ago \| parent [-]
		Sure, but I don't know what GCC's behavior is, and I don't vet behavior differences between compiler upgrades. As long as the output works, why does it matter that the black box is deterministic?

▲

rogerrogerr an hour ago | parent | prev | next [-]

I can’t remember the last time GCC emitted code that just flat out called the wrong function. If it did that occasionally, I would review it.

▲

lelanthran 43 minutes ago | parent | prev [-]

Come on, this is a take we expect from a 1st grader!

Gcc makes maybe 1 mistake ever 2 billion emissions. LLMs make 1 mistake ever 3rd emission.