AGAkash Goenkaincodebase-memory.hashnode.dev·6d ago · 6 min readNotes about code should be written by whoever read the codeI maintain a tool that keeps notes about a codebase. An agent does a task, and at the end it writes down what it worked out. There is an easier way to build this. I chose not to take it. The easier de00
AGAkash Goenkaincodebase-memory.hashnode.dev·6d ago · 13 min readFrom four tools to twoThis is an origin story told through deletions. Almost everything I consider a real design decision in this project was a removal, and each one taught me something I could not have reasoned my way to 00
AGAkash Goenkaincodebase-memory.hashnode.dev·6d ago · 8 min readThe tool the agent does not callYou can ship a tool, document it, and inject an instruction telling the agent to prefer it, and the agent will still reach for grep. Why availability is not adoption, with the mistake I shipped myself00
AGAkash Goenkaincodebase-memory.hashnode.dev·6d ago · 10 min readWhy an index of your code cannot answer the same question twiceBuilding a graph of a repository is a good idea and it works. It is also the wrong shape for one specific job that people keep expecting it to do, and the reason is not a quality problem you can fix w00
AGAkash Goenkaincodebase-memory.hashnode.dev·6d ago · 7 min readWhere the tokens go in an agent sessionA long session bills for something. The instinct is to blame the tool that returned a big block of output. That instinct is almost always wrong, and the arithmetic that explains why also tells you the00
