An AI like ChatGPT struggles to provide tech support for its own features because the product changes too rapidly. The web content and documentation it's trained on lag significantly behind the current software version, creating a knowledge gap that doesn't exist for more stable products.

Proving the ROI for developer productivity tools is challenging, as studies on their impact are often inconclusive. A more defensible business model focuses on outright automation of specific tasks (e.g., auto-updating documentation in CI). This provides a clear, outcome-oriented value proposition that is easier to sell.

Moving PRDs and other product artifacts from Confluence or Notion directly into the codebase's repository gives AI coding assistants persistent, local context. This adjacency means the AI doesn't need external tool access (like an MCP) to understand the 'why' behind the code, leading to better suggestions and iterations.

Instead of codebases becoming harder to manage over time, use an AI agent to create a "compounding engineering" system. Codify learnings from each feature build—successful plans, bug fixes, tests—back into the agent's prompts and tools, making future development faster and easier.

To avoid inconsistent or 'vibe coded' documentation, Atlassian's design system team built scripts that crawl their front-end monorepo. These scripts automatically generate structured guideline files for AI consumption by extracting component definitions, types, and usage examples directly from the production source code.

Documentation is shifting from a passive reference for humans to an active, queryable context for AI agents. Well-structured docs on internal APIs and class hierarchies become crucial for agent performance, reducing inefficient and slow context window stuffing for faster code generation.

As AI rapidly generates code, the challenge shifts from writing code to comprehending and maintaining it. New tools like Google's Code Wiki are emerging to address this "understanding gap," providing continuously updated documentation to keep pace with AI-generated software and prevent unmanageable complexity.

According to GitHub's COO, the initial concept for Copilot was a tool to help developers with the tedious task of writing documentation. The team pivoted when they realized the same underlying transformer model was far more powerful for generating the code itself.

The next IDE evolution will transform the codebase into a dynamic 'metadata backbone'. By capturing a continuous history of edits and conversations, it will allow all context—discussions, decisions, feedback—to be permanently anchored to specific lines of code, unlike today's static, snapshot-based Git workflows.