you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 13 hours ago (7 children)
  • [–] 4 points 3 hours ago* (last edited 3 hours ago) (2 children)

    This is a load of shit. AGENTS.md is just a rules file for a repo like anything else. Properly-written rules files give good direction into how to interact with a project. If you don't think it's being read, ask the agent, and figure out why.

    Far too many of these LLM articles are:

    1. I did the thing
    2. The thing didn't work for me
    3. Pretend it's a hyper-scientific experiment and write an article about it
    4. Declare X is shit because my version of X is shit, or because most people don't know how to make X.

    You don't do the thing and pretend the first draft is going to work perfectly. You iterate, ask the agent directly why it didn't work or what kind of improvements could be made, and improve the process.

    Most of the time when I'm running through a repetitive process with a skill, I ask, "hey, what pitfalls did we learn from this process and how can we improve this skill?" Boom, iteration.

    Also, Pivot-to-AI is just some guy's anti-AI blog site. He does the same shit on YouTube.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 hour ago* (last edited 59 minutes ago)

    It's literally researchers doing research which the blog links to. Most of the AI booster stuff is completely unsubstantiated, and it turns out when you measure things they are often full of shit.

  • source
  • parent
  • [–] 4 points 4 hours ago (1 child)

    Coworkers have been adding these to our projects and I have noticed no difference in the usefullness of LLMs, so I suppose it's nice to be validated.

  • source
  • parent
  • hideshow 1 child comment
  • [–] [S] 24 points 13 hours ago* (1 child)

    That blog post is based on a study that also said:

    >We conclude that while context files are useful for specifying non-standard coding practices, any attempts to improve performance should be rigorously evaluated before deployment

    The kernel project has some particular conventions and workflows, so I think in this case it may make sense.

  • source
  • parent
  • hideshow 1 child comment