A developer shares a work experience where detailed ticket documentation they wrote for their own benefit unexpectedly became valuable input for an AI-assisted frontend project. The Head of Product, using Claude to write code, fed the developer's project notes to Claude, enabling rapid alignment on system design. This prompts reflection on why developers write documentation for AI tools but not for colleagues — partly because Claude forgets everything between sessions, forcing users to write things down. The author sees a silver lining: thorough documentation habits benefit AI consumers in ways that justify the effort, and good documentation practices may actually improve in the AI era.
Sort: