12 pointsby latexr3 hours ago6 comments
  • jen729wan hour ago
    This guy – whose RSS feed I subscribe to – makes a living [0] by being anti-AI.

    That's fine. Do what you do. But don't read this article as any sort of science. It's massively opinionated rage-bait.

    [0]: https://www.patreon.com/davidgerard

    • matt_kantor33 minutes ago
      The science is the source linked in the second paragraph.
  • xg15an hour ago
    On my last project, it kept trying to use the system python instead of the project's virtual environment. It also kept using the wrong build tool. Both things wasted considerable tokens because the agent got sidetracked trying to understand why it could not run the tests - and that repeated on each new session.

    A simple instruction in AGENTS.md fixed that.

  • stuaxo2 hours ago
    It mentions that a chatbot generated AGENTS.md does nothing, which makes sense.

    I added one when it kept making the same mistake and using things from the wrong library version making compiler errors, adding in the common mistakes pre emptively.

    • Computer0an hour ago
      My agents.md usually becomes do’s don’ts and shortcuts to get to where it needs to be in the code so it doesn’t waste time and context.
  • Sha1rholderan hour ago
    “Don’t start off by git diff, git status, or git show” saved me quite a few tokens.
  • LoganDark2 hours ago
    Just because it doesn't materially impact task success rates does not mean it's not useful. I use that file to give my agent information about the environment (operating system, architecture, command-line utilities I have installed), as well as how to do certain things (such as using `uv` for running Python when needed). I want my agent to work how I do, so I also tell it things like my preferred version control system (jj), my preferred implementation languages for things like shell scripts (zsh), and other things like that. I care more about how the work is done than the final result. It still slips up sometimes, but on the whole I think it works alright. It's not like it fixes tasks that wouldn't be completed at all, but it does help my satisfaction with how they were completed, as well as with the final result. Otherwise, I'd have to do a lot more manual cleanup.
    • cyanydeezan hour ago
      I just have it comment on scripts, I've now just started for an app super-run.sh consisting of this pipeline: dev, test, build, e2e, deploy.

      All the scripts are designed to bail quickly. They all create a log in the background instead of blocking. They're all annotated with the necessary comments to keep it on path and locate files, track pratfalls, etc.

      So any entrypoint to whatever I'm doing typically starts with one of these scripts. It's heavy handed but orientating your agent for the specific task is better than just dumping a whole set of context that will be ignored if it has nothing to do with your very next command.

      Telling it how to do a pull request isn't going to help if you're trying to debug a technical issue.

  • lazidean hour ago
    Like all LLM related issues, it doesn't until it does. Or does until it doesn't.

    Either way, you get no visibility or predictability.

    Good luck.