https://abbreviatory.com/tags/directory-listings/ Recent content in directory listings on Abbreviatory.com Hugo -- gohugo.io en-us Mon, 19 Oct 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-0.4-reads-git-diffs-http-responses-and-directory-listings/ Mon, 19 Oct 2026 00:00:00 +0000 https://abbreviatory.com/abbreviatory-0.4-reads-git-diffs-http-responses-and-directory-listings/ Test runs and logs aren’t the only big outputs a coding agent reads. It reads diffs all day, to review what it changed. It calls APIs with curl and gets back a wall of JSON. It runs find to see what’s in a repository, and gets ten thousand paths. Abbreviatory v0.4.0 reads all three. Each one gets rules of its own, because each one has its own idea of what matters. https://abbreviatory.com/how-to-map-an-unfamiliar-repository-with-find-and-abbreviatory/ Mon, 19 Oct 2026 00:00:00 +0000 https://abbreviatory.com/how-to-map-an-unfamiliar-repository-with-find-and-abbreviatory/ The first thing anyone does in a new repository is look around. A person runs tree and gives up after a few screens. A coding agent runs find . -type f and gets every path, and on a large project that’s thousands of lines spent before it has read a single file. Most of them say the same thing: another test fixture, another Go file in the same package. The listing in this example is find src -type f over Go’s own source tree, which is big enough to make the point: 10,703 paths in 1,097 directories, 454.