@hanshuebner Thanks but I guess I will see the effects of using LLMs over a longer period of time on a bigger codebase at work anyway. I'm actually more concerned about the effects on the developers, which brings us back to Arne's original toot.
@grishka @plexus
schaueho@functional.cafe
Posts
-
It's clear that AI assisted coding is dividing developers (welcome to the culture wars!). -
It's clear that AI assisted coding is dividing developers (welcome to the culture wars!).@hanshuebner What does "software is better" even mean in this context?
I wonder if this entire "LLM generated code is good enough and it's creation is much more efficient" argument will stand the test of time when a lot of code is generated on the same product / project by many people. We do not know the answer to this yet.
@grishka -
First example we at MELPA have seen of an #emacs package getting hacked (upstream of us, in GitHub): https://github.com/kubernetes-el/kubernetes-el/issues/383@sanityinc Then the risk of this is not increased (at least not too much) when considering root.
However, given that there are still files that only root can access and things that only root can change on a system, I actually think that usually the risk would be higher for root. But it's not a big point, agreed.
@loke @alex @tzz -
First example we at MELPA have seen of an #emacs package getting hacked (upstream of us, in GitHub): https://github.com/kubernetes-el/kubernetes-el/issues/383@alex I mostly use jed as root, that's usually good enough for the minor editing needs I have as root. Everything that requires more comfort and capabilities will be done with my normal account and then run as root.
@loke @sanityinc @tzz