Your company's docs are lying to you. A graph can tell you which ones.
# Your company's docs are lying to you. A graph can tell you which ones. At most companies, "why do we use Kafka?" has an answer. It's in ADR-007, written two years ago by someone who has since left. And the onboarding guide, the ledger runbook and the event-schema doc were all written assuming Kafka. If the team switches to Redpanda next week, all three are wrong the moment the decision is made,…
Companies often provide outdated documentation for their systems, leading to confusion and errors when changes are made. A graph database called WhyBase can help identify which documents are no longer accurate and who should update them. The system stores relationships between people, teams, systems, projects, decisions and sources as nodes and edges in a graph. By querying the graph, users can find stale documentation and the correct, up-to-date systems and people responsible for fixing them.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
