---
schema_version: '1.0'
id: news-20260814-9b530a
title: なぜベテランの暗黙知は、文書化しても継承できないのか | DevelopersIO
url: https://dev.classmethod.jp/articles/why-tacit-knowledge-cannot-be-documented/
url_hash: 9b530a79074fe51f3a66c4036e1cc38b8f222e9efd960b55b8692092c09dcfb5
canonical_url: https://dev.classmethod.jp/articles/why-tacit-knowledge-cannot-be-documented
source: dev.classmethod.jp
category: news/tech
category_raw: technology
region: null
tags:
- technology
- knowledge_management
- implicit_knowledge
- manuals
- experience_transfer
- llm
lang: null
published_at: null
fetched_at: '2026-08-14T06:00:59.349364Z'
updated_at: '2026-08-20T20:08:39.870796Z'
status: published
content_hash: null
content_changed_at: null
license_note: link-only
summary: null
summary_source: null
summary_en: null
summary_omitted_reason: license_restricted
redistribution: false
keywords_en:
- DevelopersIO
- experience_transfer
- general news
- implicit_knowledge
- knowledge_management
- LLM
- manuals
- technology
entities_en:
- name: LLM
  type: concept
- name: technology
  type: concept
topics_en:
- general news
numeric_facts: []
entities:
- name: technology
  type: concept
- name: LLM
  type: concept
key_facts: []
related: []
related_auto:
- name: hacking_group
  type: organization
  weight: 1.0
- name: Manus
  type: organization
  weight: 1.0
- name: Uber_Freight
  type: organization
  weight: 1.0
- name: bottleneck
  type: UNKNOWN
  weight: 1.0
computed_at: null
sanitized_at: '2026-08-20T14:56:50.092484+00:00'
---

# なぜベテランの暗黙知は、文書化しても継承できないのか | DevelopersIO

## TL;DR
（要約なし・原文はリンク先を参照 / No summary available; see the source link.）

## Key Points
- technology / knowledge_management / implicit_knowledge / manuals / experience_transfer / llm

## Details
(本文なし。リンク先参照)

## Source
元記事: [なぜベテランの暗黙知は、文書化しても継承できないのか | DevelopersIO](https://dev.classmethod.jp/articles/why-tacit-knowledge-cannot-be-documented/)