--- title: "#keepthewhy articles | Hashnode" description: "Explore 12 articles tagged #keepthewhy on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/keepthewhy" --- Tag # #keepthewhy 12 posts · 0 followers [Oliver Zehentleitner](https://hashnode.com/@oliver-zehentleitner) · [Nov 6](https://hashnode.com/posts/keep-the-why-s-dashboard-is-now-a-library-and-maity-is-its-second-host/6aedca89485f91d9b82bde80) ### [Keep the Why's dashboard is now a library, and Maity is its second host](https://blog.technopathy.club/keep-the-why-s-dashboard-is-now-a-library-and-maity-is-its-second-host?utm_source=hashnode&utm_medium=feed) The views that read a project's reasons (graph, timeline, thoughts, family) can now be mounted by any page. Maity shows them next to the board. 5 min read · [blog.technopathy.club](https://blog.technopathy.club/keep-the-why-s-dashboard-is-now-a-library-and-maity-is-its-second-host?utm_source=hashnode&utm_medium=feed) [2](https://hashnode.com/posts/keep-the-why-s-dashboard-is-now-a-library-and-maity-is-its-second-host/6aedca89485f91d9b82bde80) [Oliver Zehentleitner](https://hashnode.com/@oliver-zehentleitner) · [Oct 12](https://hashnode.com/posts/keep-the-why-vs-past-dev-vs-agent-memory-repo-vs-agentmemory/6acca24978f7ababf985dcb8) ### [Keep the Why vs. past.dev vs. Agent Memory Repo vs. agentmemory](https://blog.technopathy.club/keep-the-why-vs-past-dev-vs-agent-memory-repo-vs-agentmemory?utm_source=hashnode&utm_medium=feed) Four tools called agent memory. Four different approaches to what should survive. One puts decision rationale next to the code. 13 min read · [blog.technopathy.club](https://blog.technopathy.club/keep-the-why-vs-past-dev-vs-agent-memory-repo-vs-agentmemory?utm_source=hashnode&utm_medium=feed) [Oliver Zehentleitner](https://hashnode.com/@oliver-zehentleitner) · [Oct 5](https://hashnode.com/posts/keep-the-why-vs-okf-agent-memory-vs-repowise-three-approaches-to-git-native-project-memory/6ac3c0863a67f8994a6d5474) ### [Keep the Why vs. OKF Agent Memory vs. RepoWise: Three Approaches to Git-Native Project Memory](https://blog.technopathy.club/keep-the-why-vs-okf-agent-memory-vs-repowise-three-approaches-to-git-native-project-memory?utm_source=hashnode&utm_medium=feed) Rationale, structured knowledge, or codebase intelligence for coding agents? 16 min read · [blog.technopathy.club](https://blog.technopathy.club/keep-the-why-vs-okf-agent-memory-vs-repowise-three-approaches-to-git-native-project-memory?utm_source=hashnode&utm_medium=feed) [2](https://hashnode.com/posts/keep-the-why-vs-okf-agent-memory-vs-repowise-three-approaches-to-git-native-project-memory/6ac3c0863a67f8994a6d5474) [Oliver Zehentleitner](https://hashnode.com/@oliver-zehentleitner) · [Oct 5](https://hashnode.com/posts/the-model-changed-my-skill-didn-t-the-score-still-dropped/6ac3cdcb13d6c7ff530ab3f4) ### [The Model Changed. My Skill Didn't. The Score Still Dropped.](https://blog.technopathy.club/the-model-changed-my-skill-didn-t-the-score-still-dropped?utm_source=hashnode&utm_medium=feed) What agent evals taught me about moving model floors, noisy LLM judges, and treating the evaluator as part of the instrument 9 min read · [blog.technopathy.club](https://blog.technopathy.club/the-model-changed-my-skill-didn-t-the-score-still-dropped?utm_source=hashnode&utm_medium=feed) [Oliver Zehentleitner](https://hashnode.com/@oliver-zehentleitner) · [Sep 29](https://hashnode.com/posts/the-reasoning-behind-a-codebase-as-a-web-you-can-walk/6abc0e2fcbb7082b897b890a) ### [The reasoning behind a codebase, as a web you can walk](https://blog.technopathy.club/the-reasoning-behind-a-codebase-as-a-web-you-can-walk?utm_source=hashnode&utm_medium=feed) Decisions that cite each other across repositories — no graph database, no central index, no account. Just Markdown and Git. 9 min read · [blog.technopathy.club](https://blog.technopathy.club/the-reasoning-behind-a-codebase-as-a-web-you-can-walk?utm_source=hashnode&utm_medium=feed) [4](https://hashnode.com/posts/the-reasoning-behind-a-codebase-as-a-web-you-can-walk/6abc0e2fcbb7082b897b890a) [Oliver Zehentleitner](https://hashnode.com/@oliver-zehentleitner) · [Sep 22](https://hashnode.com/posts/keep-the-why-vs-claude-code-auto-memory-vs-memorycustodian-vs-agentsroom/6ab28b9d1e5cee7483b794bc) ### [Keep the Why vs. Claude Code Auto Memory vs. MemoryCustodian vs. AgentsRoom](https://blog.technopathy.club/keep-the-why-vs-claude-code-auto-memory-vs-memorycustodian-vs-agentsroom?utm_source=hashnode&utm_medium=feed) Four tools that get called project memory. Three questions sort them. One table, as of September 2026. 13 min read · [blog.technopathy.club](https://blog.technopathy.club/keep-the-why-vs-claude-code-auto-memory-vs-memorycustodian-vs-agentsroom?utm_source=hashnode&utm_medium=feed) [17](https://hashnode.com/posts/keep-the-why-vs-claude-code-auto-memory-vs-memorycustodian-vs-agentsroom/6ab28b9d1e5cee7483b794bc) [Oliver Zehentleitner](https://hashnode.com/@oliver-zehentleitner) · [Sep 9](https://hashnode.com/posts/one-index-many-writers-avoiding-git-merge-conflicts-with-deterministic-write-areas/6aa1a640f3a6f898eb822819) ### [One Index, Many Writers: Avoiding Git Merge Conflicts with Deterministic Write Areas](https://blog.technopathy.club/one-index-many-writers-avoiding-git-merge-conflicts-with-deterministic-write-areas?utm_source=hashnode&utm_medium=feed) How a small structural change reduced unnecessary Git conflicts in a shared Markdown index — and made it easier for coding agents to navigate. 4 min read · [blog.technopathy.club](https://blog.technopathy.club/one-index-many-writers-avoiding-git-merge-conflicts-with-deterministic-write-areas?utm_source=hashnode&utm_medium=feed) [4](https://hashnode.com/posts/one-index-many-writers-avoiding-git-merge-conflicts-with-deterministic-write-areas/6aa1a640f3a6f898eb822819) [Oliver Zehentleitner](https://hashnode.com/@oliver-zehentleitner) · [Sep 8](https://hashnode.com/posts/what-happens-when-a-coding-agent-forgets-why-a-change-was-rejected/6aa015bcbe03d2ac71a46645) ### [What happens when a coding agent forgets why a change was rejected?](https://blog.technopathy.club/what-happens-when-a-coding-agent-forgets-why-a-change-was-rejected?utm_source=hashnode&utm_medium=feed) I tested what a fresh coding-agent session does when the repo remembers the code, but not the reasoning behind it. 5 min read · [blog.technopathy.club](https://blog.technopathy.club/what-happens-when-a-coding-agent-forgets-why-a-change-was-rejected?utm_source=hashnode&utm_medium=feed) [10](https://hashnode.com/posts/what-happens-when-a-coding-agent-forgets-why-a-change-was-rejected/6aa015bcbe03d2ac71a46645) [Oliver Zehentleitner](https://hashnode.com/@oliver-zehentleitner) · [Aug 24](https://hashnode.com/posts/same-skill-six-agents-nine-models-what-a-real-eval-matrix-taught-me/6a8c482e14caf5cf1bf21e0d) ### [Same Skill, Six Agents, Nine Models: What a Real Eval Matrix Taught Me](https://blog.technopathy.club/same-skill-six-agents-nine-models-what-a-real-eval-matrix-taught-me?utm_source=hashnode&utm_medium=feed) I ran the same skill and the same task through different coding agents. The model mattered. But the agent harness changed the outcome far more than I expected. 15 min read · [blog.technopathy.club](https://blog.technopathy.club/same-skill-six-agents-nine-models-what-a-real-eval-matrix-taught-me?utm_source=hashnode&utm_medium=feed) [Oliver Zehentleitner](https://hashnode.com/@oliver-zehentleitner) · [Jul 28](https://hashnode.com/posts/keep-the-why-project-memory-for-humans-and-ai-agents/6a68718d02692692c296b1b9) ### [Keep the Why: Project Memory for Humans and AI Agents](https://blog.technopathy.club/keep-the-why-project-memory-for-humans-and-ai-agents?utm_source=hashnode&utm_medium=feed) How a simple rationale-capture skill evolved into a repository-native knowledge lifecycle without a database, daemon, or dashboard. 16 min read · [blog.technopathy.club](https://blog.technopathy.club/keep-the-why-project-memory-for-humans-and-ai-agents?utm_source=hashnode&utm_medium=feed) [2](https://hashnode.com/posts/keep-the-why-project-memory-for-humans-and-ai-agents/6a68718d02692692c296b1b9)