←back to thread

75 points throwaway-ai-qs | 1 comments | | HN request time: 0s | source

Between code reviews, and AI generated rubbish, I've had it. Whether it's people relying on AI to write pull request descriptions (that are crap by the way), or using it to generate tests.. I'm sick of it.

Over the year, I've been doing a tonne of consulting. The last three months I've watched at least 8 companies embrace AI generated pip for coding, testing, and code reviews. Honestly, the best suggestions I've seen are found by linters in CI, and spell checkers. Is this what we've come to?

My question for my fellow HNers.. is this what the future holds? Is this everywhere? I think I'm finally ready to get off the ride.

Show context
Herring ◴[] No.45279184[source]
AI will keep improving

https://epoch.ai/blog/can-ai-scaling-continue-through-2030

https://epoch.ai/blog/what-will-ai-look-like-in-2030

There's a good chance that eventually reading code will become like inspecting assembly.

replies(3): >>45279227 #>>45279264 #>>45280705 #
epicureanideal ◴[] No.45279264[source]
> There's a good chance that eventually reading code will become like inspecting assembly.

We don’t read assembly because we read the higher level code, which deterministically is compiled to lower level code.

The equivalent situation for LLMs would be if we were reviewing the prompts only, and if we had 100% confidence that the prompt resulted in code that does exactly what the prompt asks.

Otherwise we need to inspect the generated code. So the situation isn’t the same, at least not with current LLMs and current LLM workflows.

replies(1): >>45279509 #
1. YeGoblynQueenne ◴[] No.45279509[source]
>> We don’t read assembly because we read the higher level code, which deterministically is compiled to lower level code.

I think the reason "we" don't read, or write, assembly is that it takes a lot of effort and a detailed understanding of computer architecture that are simply not found in the majority of programmers, e.g. those used to working with javascript frameworks on web apps etc.

There are of course many "we" who work with assembly every day: as a for instance, people working with embedded systems, or games programmers as another.