~/blog · filtered by category

knowledge.

9 entries filed under this signal. ← back to all entries

[blog/category/knowledge] · reverse chronological $ ls -la --filter=knowledge

2026-07-20 knowledge Tribal knowledge is a single point of failure The one person who knows why that module exists is a risk you priced at zero. Now half your new hires are agents who never met them. #paelladoc#knowledge-graph#tribal-knowledge#onboarding#ai-coding 8 min ./read → 2026-07-20 knowledge Reading a repo into product artifacts: stories, criteria, decisions Everyone teaches the forward path: spec first, then build. For software that already exists you need the reverse, and almost nobody explains it. #paelladoc#knowledge-graph#reverse-intake#acceptance-criteria#ai-coding 9 min ./read → 2026-07-20 knowledge Product memory: what your team forgets and your system shouldn't Teams don't forget the code. They forget the decisions, the reasons, and the dead ends. When nothing remembers those, you keep re-litigating settled questions and agents keep re-walking paths you already abandoned. #paelladoc#product-memory#decision-logs#knowledge-graph#ai-coding 9 min ./read → 2026-07-20 knowledge Onboard against the graph, not tribal knowledge A new hire ramps by asking the person next to them. So does a new agent, except it can't. Both should onboard against a graph of the system, not a map trapped in someone's head. #paelladoc#onboarding#knowledge-graph#tribal-knowledge#agents 8 min ./read → 2026-07-20 knowledge Living documentation: docs that stop rotting Docs rot because they're a second copy of the truth that nobody keeps in sync. The only version that stays current is the one derived from the system, not written beside it. #paelladoc#living-documentation#docs-as-code#knowledge-graph#ai-coding 8 min ./read → 2026-07-20 knowledge Knowledge graph vs vector search for code: when each one wins Embedding your whole codebase and hoping the right chunks come back is the default. It works, until the question is about relationships instead of resemblance. #paelladoc#knowledge-graph#rag#retrieval#ai-coding 9 min ./read → 2026-07-20 knowledge Docs-as-code in the agent era Docs-as-code was already good practice. Once agents read your docs to decide what to build, the docs pipeline stops being a nice-to-have and becomes part of the build. #paelladoc#knowledge-graph#docs-as-code#living-documentation#ai-coding 9 min ./read → 2026-07-20 knowledge Codebase maps, not bigger prompts When an agent keeps getting it wrong, the reflex is to write a longer prompt. The agent doesn't need more words about the codebase. It needs a map of it. #paelladoc#codebase-maps#ai-coding#agents#context-engineering 8 min ./read → 2026-07-20 knowledge Code knowledge graphs: what they are and why agents need them An agent can read any file in your repo on demand. What it can't do is see how the files relate. That map is a code knowledge graph, and it's the difference between a change that fits and one that breaks three files away. #paelladoc#knowledge-graph#ai-coding#codebase-maps#agents 11 min ./read →

— end of log · 9 entries in knowledge —