[CurleighBraces]

I find talking to LLMs both amazing and frustrating, a computer that can understand my plain text ramblings is incredible, but it's inability to learn is frustrating.

A good example, with junior developers I create thorough specs first and as I saw their skills and reasoning abilities progress my thoroughness drops as my trust in them grows. You just can't do that with LLMs

[raffraffraff]

You can write an agent.md file and gradually add to it as you develop the project. The reason junior developers get better is that the context goes from low to high over the time you spend working with them. Yes, "learning".

I've found that maintaining a file that is designed to increase the LLM's awareness of how I want to approach problems, how I build / test / ship code etc, leads to the LLM making fewer annoying assumptions.

Almost all of the annoying assumptions that the LLM makes are "ok, but not how I want it done". I've gotten into the habit of keeping track of these in a file. Like the 10 commandments for LLMs. Now, whenever I'm starting a new context I drop in an agent.md and tell it to read that before starting. Fella like watching Trinity learn how to fly a helicopter before getting into it.

It's still not perfect, but I'm doing waaaay more work now to get annoyed by the LLM's inability to "automatically learn" without my help.

[CurleighBraces]

There's limits to AGENTS.md too, a junior will start to understand the concepts/rationale and design decisions and be able to apply that knowledge to future problems, the LLM will not.

It's way too literally in its thinking.