Credit where credit is due
42 points - last Friday at 5:53 PM
SourceComments
I use LLMs every day at work. At the same time, I've never had an LLM appear as a "co-author", not because I'm making any effort to hide my LLM use, but because I've never been comfortable letting an LLM commit code. I use staging changes, hunk by hunk (or sometimes even line-by-line), as my review process. I don't want LLMs performing any git operations that add or push commits. I imagine I'm not the only one.
PS: If you want some bumpers to help avoid having your LLMs commit code, configuring Git for commit signing and blocking access to your signing key, agent socket, write access to your local Git config, etc., is pretty effective in my experience.
[0]: https://marcusolang.substack.com/p/im-kenyan-i-dont-write-li...
And they have the audacity to claim that the public will defund them if they don't use new tech. No, the public will defund you if you continue cheating like a 10 year old and you are evidently superfluous.
Just say no!
Clearly not written by LLM. (NB: emphasis mine)
I undersign everything under my imprimatur; LLM, contract programmer, intern, whatever. If it has my chop; it has my support and accountability.
The "A" word (Accountability) has been getting deprecated far longer than LLMs have been around. It seems that no one wants to stand behind their work, anymore; regardless of how that work was done.
I had the advantage of spending almost 27 years, at a company that really made sure that I was Accountable. I ran a team, but it was my butt on the line.