I've been thinking on a similar line, but because I work on graph data in append-only style (Datomic db) I've inevitably been thinking about how decisions in a team on large projects are a growing knowledge graph. I'm pretty convinced that markdown is higher noise to signal than we actually need for an effective LLM tool like this.
I have also seen LLMs operate on Datomic insanely faster than reading directories of markdown files to resolve information and links between information in my system, so why not shift the information about building my system to there too?!
Thank you! You're right, markdown is not going to scale over time in larger projects. I've been thinking about testing different storage and retrieval solutions but keeping the same code "anchoring" and overall process.
With a more robust harness than the current loose collection of skills + bash script one could offer freedom of choice between a number of storage & retrieval options. After all, markdown gives a very low barrier of entry and makes for an easy evaluation, so I'd rather keep it but support an option for larger projects.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Love this idea and execution. Great write-up
I've been thinking on a similar line, but because I work on graph data in append-only style (Datomic db) I've inevitably been thinking about how decisions in a team on large projects are a growing knowledge graph. I'm pretty convinced that markdown is higher noise to signal than we actually need for an effective LLM tool like this.
I have also seen LLMs operate on Datomic insanely faster than reading directories of markdown files to resolve information and links between information in my system, so why not shift the information about building my system to there too?!
Thank you! You're right, markdown is not going to scale over time in larger projects. I've been thinking about testing different storage and retrieval solutions but keeping the same code "anchoring" and overall process.
With a more robust harness than the current loose collection of skills + bash script one could offer freedom of choice between a number of storage & retrieval options. After all, markdown gives a very low barrier of entry and makes for an easy evaluation, so I'd rather keep it but support an option for larger projects.