Programmers will document for Claude, but not for each other
blog.plover.com
Programmers will document for Claude, but not for each other
1–10 of 166 posts
Re: Programmers will document for Claude, but not for each other
#2sure, but those documents are generally just as useless because they're 70% complete, 10% indirect and 20% wrong.
Unstrutuced slop is no better at best, and much worse at worst.
Re: Programmers will document for Claude, but not for each other
#31. Claude's productivity is your productivity, but team's productivity is not your productivity.
2. Claude will actually read what is written (well parse for autocompletion, not actually "read", unless you are under AI-psychosis).
Re: Programmers will document for Claude, but not for each other
#4Some people like to brag about how productive they have become with AI, but I see them spending a few hours a week adjusting which model to use, trying the new shiny harness or writing Claude skills.
Are you really more productive if instead of coding you are spending your time tweaking the AI to do what you want?
Re: Programmers will document for Claude, but not for each other
#5sure, but those documents are generally just as useless because they're 70% complete, 10% indirect and 20% wrong. Unstrutuced slop is no better at best, and much worse at worst.
Slop in, slop out.
The new GIGO?
Re: Programmers will document for Claude, but not for each other
#6yeah, because claude will actually read the docs
Re: Programmers will document for Claude, but not for each other
#7Some people like to brag about how productive they have become with AI, but I see them spending a few hours a week adjusting which model to use, trying the new shiny harness or writing Claude skills. Are you really more productive if instead of coding you are spending your time tweaking the AI to do what you want?
eh, that seems like the least harmful part of this entire thing, we've had that for decades https://www.youtube.com/watch?v=urcL86UpqZc
Re: Programmers will document for Claude, but not for each other
#8sure, but those documents are generally just as useless because they're 70% complete, 10% indirect and 20% wrong. Unstrutuced slop is no better at best, and much worse at worst.
Ahh yes, the documentation for claude.
When someone created a CLAUDE.md, then changed some stuff around and when I later had to touch that repository my claude was hallucinating classes, functions and architecture that was already long gone!
I just deleted the CLAUDE.md, since I had no mood to "fix" it.
Re: Programmers will document for Claude, but not for each other
#9I've written so much documentation over the years, and humans always come and ask me questions that the documentation answers, but never ever read it.
Re: Programmers will document for Claude, but not for each other
#10I've been noticing that too. "Hey, the normal documentation for our software of a crude API list describing what each command is and each of its parameters isn't good enough for the AI. We need to provide the AI with instructions on how to use the software to solve common problems"
Uh, you needed to do that for humans too. You just didn't. There's a reason everybody scrolls to the bottom of man pages ASAP.