Isn’t this just kicking the can down the road? > but the LLM is rediscovering knowledge from scratch on every question Unless the wiki stays fully in context now the LLM hast to re-read the wiki instead of re-reading the source files. Also this will introduce and accumulate subtle errors as we start to regurgitate 2nd-order information. I totally get the idea but I think next gen models with 10M context and/or 1000tp…
I use a home baked system based on obsidian that is essentially just “obsidian but with structured format on top with schemas” and I deploy this in multiple places with ranges of end users. It is more valuable than you think. The intermediary layer is great for capturing intent of design and determining when implementation diverges from that. There will always be a divergence from the intent of a system and how it ac…
LLM Wiki – example of an "idea file"
71–80 of 109 posts
Re: LLM Wiki – example of an "idea file"
#72I've recently lazied out big time on a company project going down a similar rabbit hole. After having a burnout episode and dealing with sole caregiver woes in the family for the past year, I've had less and less energy to piece together intense, correct thought sequences at work. As such I've taken to delegating substantial parts architecture and discovery to multiagent workflows that always refer back to a wiki-lik…
Me too, and I wonder where this will take us; I worry about losing the ability to think hard.
Re: LLM Wiki – example of an "idea file"
#73I don't think this is taking it as far as it can go. Everything should live in the repo. Code and docs yes. But also the planning files, epics, work items, architectural documentation and decisions. Here is a small example of my Linux system doc: https://github.com/gchamon/archie/tree/main/docs And you don't need to reinvent the wheel. Code docs can like either right next to it in the readme or in docs/ if it's too b…
> Everything should live in the repo. Code and docs yes. But also the planning files, epics, work items, architectural documentation and decisions. You just described spec-driven development.
Re: LLM Wiki – example of an "idea file"
#74Earlier quoted context omitted.
The article is not on training LLMs. it is about using LLMs to write a wiki for personal use. The article assumes a fully trained LLM such as ChatGPT or Claude already exists to be used.
Don't even try, after vibe coding, people seem to be adopting vibe thinking. "Model Collapse sounds cool, I'm gonna use it without looking up"
Re: LLM Wiki – example of an "idea file"
#75Earlier quoted context omitted.
You’re not doing anything wrong. This isn’t a bulletproof idea. It can work, and this is what a lot of people end up with to manage complexity, but there’s a critical point beyond which things collapse: the agent can’t keep the wiki up to date anymore, the developer can’t grok it anymore.
Managing complexity, modularity, separation of concerns, were already critical for ensuring humans could still hold enough of the system in their brains to do something useful. People who do not understand that will continue to not understand that it also applies to AI right now. Maybe at some point in the future it won't, not sure. But my impression is that systems grow in complexity far past the point where the sys…
I think this is mostly a matter of expectation management. AIs are being positioned as being able to develop software independently, and that’s certainly the end goal.
So then people come in with the expectation that the AI is able to manage that, and it fails. Spectacularly.
The LLM can certainly not manage any non-local complexity right now, and succeed in increasing the technical debt and complexity faster than ever before.
Re: LLM Wiki – example of an "idea file"
#76Earlier quoted context omitted.
> He really wants to shine, but how is this different than claude memory or skills? It isn't different. This just tries to reinvent the wheel that all mainstream coding assistants have been providing for over a year. Even ChatGPT rolled out chat memory in their free tier.
The difference obviously being, his way you own the memories; in what's currently deployed, it's the platform that owns them.
I don't think you are very familiar with the state of LLM assistants. Prompt files were a thing since ever, and all mainstream coding assistants support storing your personal notes in your own files in multiple ways. Prompt files, instruction files, AGENTS.md, etc.
Re: LLM Wiki – example of an "idea file"
#77Re: LLM Wiki – example of an "idea file"
#78Isn’t this just kicking the can down the road? > but the LLM is rediscovering knowledge from scratch on every question Unless the wiki stays fully in context now the LLM hast to re-read the wiki instead of re-reading the source files. Also this will introduce and accumulate subtle errors as we start to regurgitate 2nd-order information. I totally get the idea but I think next gen models with 10M context and/or 1000tp…
Re: LLM Wiki – example of an "idea file"
#79Re: LLM Wiki – example of an "idea file"
#80I've recently lazied out big time on a company project going down a similar rabbit hole. After having a burnout episode and dealing with sole caregiver woes in the family for the past year, I've had less and less energy to piece together intense, correct thought sequences at work. As such I've taken to delegating substantial parts architecture and discovery to multiagent workflows that always refer back to a wiki-lik…
> I miss thinking harder Me too, and I wonder where this will take us; I worry about losing the ability to think hard.