I have used the new template below to show how it looks. We can add more details to the linked CONTRIBUTING.md in the pop repo.
I have not included any LLM (also known as AI) generated content in...
The issue for now is LLM generation of code, not code auditing.
And no, I don’t give a fuck whether some genius in theory could paint s new Mona Lisa with it.
The issue us how it is used in practice, most of the time, today.
At $WORK, I have a severely ai-pilled Senior Embedded Software Architect which hasnt managed in one and a half year to set up a working driver for a RS232-controlled stepper motor, from a port of previously working code. A thing that should take a week at most. I had to educate him that in C++ drivers, you need to use locks or mutexes to access variables that are concurrently changed and read from several threads. AI enables catastrophic levels of incompetence.
And FOSS projects need to protect themselves against that.
I’ve found ‘senior’ staff that became talking heads and stopped doing real work the bane of my existence in GenAI world. “I haven’t coded in 20 years, but thanks to GenAI, I’m doing it again!” The reasons you stopped coding 20 years ago are plainly valid. Good for you, you got to transition to a grift based career where you say nothing but sound smart to the right people and get money, please don’t return to coding because CodeGen is now ‘cool’.
Yeah… LLM Generation I agree is the biggest issue by far.
On the Kernel side, code review though apparently has been a big factor apparently, because people are testing kernel modules in seriously dumb tests that would never happen in practice, and then submitting some of the dumbest patches to protect against faults that won’t happen in reality
Oh man, the insane defensive code that it wants to generate. Yes, a decent principle, but when the stack has checked the same thing like 4 times, it’s a bit much.
The issue for now is LLM generation of code, not code auditing.
And no, I don’t give a fuck whether some genius in theory could paint s new Mona Lisa with it. The issue us how it is used in practice, most of the time, today. At $WORK, I have a severely ai-pilled Senior Embedded Software Architect which hasnt managed in one and a half year to set up a working driver for a RS232-controlled stepper motor, from a port of previously working code. A thing that should take a week at most. I had to educate him that in C++ drivers, you need to use locks or mutexes to access variables that are concurrently changed and read from several threads. AI enables catastrophic levels of incompetence.
And FOSS projects need to protect themselves against that.
I’ve found ‘senior’ staff that became talking heads and stopped doing real work the bane of my existence in GenAI world. “I haven’t coded in 20 years, but thanks to GenAI, I’m doing it again!” The reasons you stopped coding 20 years ago are plainly valid. Good for you, you got to transition to a grift based career where you say nothing but sound smart to the right people and get money, please don’t return to coding because CodeGen is now ‘cool’.
Yeah… LLM Generation I agree is the biggest issue by far.
On the Kernel side, code review though apparently has been a big factor apparently, because people are testing kernel modules in seriously dumb tests that would never happen in practice, and then submitting some of the dumbest patches to protect against faults that won’t happen in reality
Oh man, the insane defensive code that it wants to generate. Yes, a decent principle, but when the stack has checked the same thing like 4 times, it’s a bit much.