Agents.md May Trick Us Into Writing Better Docs
Key topics
As AI-powered coding assistants gain traction, a provocative question emerges: will the need for detailed documentation to feed these tools prompt developers to write better docs? Some commenters share concerns about the token usage costs associated with elaborate docstrings, while others argue that comments are meant for human developers, not machines, and should be kept separate from AI training data. One developer shares a practical approach, condensing comments into brief summaries with links to external documentation. The consensus seems to be that documentation is still essential, and the key is to be mindful of what's fed to AI tools.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
4h
Peak period
3
9-10h
Avg / period
2.5
Key moments
- 01Story posted
Aug 26, 2025 at 6:57 AM EDT
4 months ago
Step 01 - 02First comment
Aug 26, 2025 at 11:10 AM EDT
4h after posting
Step 02 - 03Peak activity
3 comments in 9-10h
Hottest window of the conversation
Step 03 - 04Latest activity
Aug 26, 2025 at 4:12 PM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
We might need new ways to document code.
The core agent files links out to architectural and product decisions as well (i have a /docs folder for them)
This works better for me and I can get a good result when asking to make sure docs are updated whenever changes are made
trust me, the future you will thank you