Why do teams keep losing context, and why hasn't any tool fixed it?
Engineering teams lose context as knowledge gets scattered across Confluence, Notion, Git, and Slack. The real bottleneck isn't code generation but the loss of the "why" behind decisions, leading to slow onboarding and AI suggestions that are correct locally but wrong architecturally.
Background
- A Hacker News discussion about a classic engineering problem: team knowledge lives scattered across Confluence docs, Notion pages, Git history, and Slack threads — with the crucial "why" behind decisions often trapped in people's heads. New hires must reconstruct it all from scratch.
- Confluence and Notion are collaboration/documentation platforms. Git is the standard version-control system for code. Slack is a messaging app where much real-time technical discussion happens but is hard to search retroactively.
- The post argues AI coding assistants (like Copilot) aren't helpful here: they see the code ("what") but not the design rationale, discarded alternatives, or business constraints ("why"). So AI can suggest code that's locally correct but architecturally wrong.
- "Context continuity" = the unsolved problem of preserving a team's full reasoning about a system across turnover and time.