• As long as my system stays stable, and it is properly noted in the code, idk.

    If at this point every major codebase is using AI for development, and AI is unavoidable, might as well embrace it on your own terms.

    • Laziest attitude. An excuse to just comply and conform. If it’s something you oppose, then fucking oppose it. Your expression of apathy is what most people do, but plenty don’t really want to. Then grow a spine. No offense with my hyperbole.

      • 4 days

        By all means, exercise that spine.

        Will you also be ignoring the new CVEs if they’re discovered using AI?

        • I don’t know what that is; not a professional developer. And I truly meant when I said no offense because I was simply latching onto your comment to address the principle. If you - or whomever - don’t have a problem with integrating AI, then my statement isn’t directed toward you. It seemed based on your wording, that you’re opposed to it but accept the inevitability and therefore embrace it. That’s exactly what allows it to flourish - everyone sharing that reaction.

          • 3 days

            CVE stands for Common Vulnerabilities and Exposures - this is the reporting system that describes problems with various versions of various software and operating system components / configurations. They generally don’t publish them until a fix is also available. These are the things that tell people: if you don’t upgrade your XYZ an attacker can take control of your system, execute arbitrary code, without you doing anything except connecting to a network the attacker has access to… AI is finding, and fixing, CVEs at about 5-10x the rate that people were finding them without AI 2 years ago.

            For me, it’s an example of: if you don’t participate in AI things and make the extra new patches coming out, the attackers who do use AI things are going to pwn your systems with them. Doesn’t matter if you’re a professional developer or not, if you use a computer, you need to apply the patches and updates, if you “opt out of all things AI” you’re just going to be vulnerable.

            Stuff like that doesn’t leave a good way to opt out, the environment is changing and if you don’t go with it, you’re going to be victimized by it.

            • I agree that’s something you need to pay attention to, for sure. That doesn’t mean all developers therefore need to use AI in their applications, it just means you should stay up to date and aware of these things.

    • Most things are only inevitable if accepted. Human history is plagued with things that never should have been considered, let alone accepted.

            • The slavery reference was an example of people accepting things that clearly should not be accepted.

              You are a deliberate waste of space.

              • Again, the suggestion that new forms of automation should not be accepted on the same basis as slavery is imbecilic beyond belief. You are a clown.

    • 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.

      • Yeah I had one trying to start an initiative to add them and when I asked how they know if they’re doing anything he was completely at a loss for words. It is just cargo cult mentality.

    • 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.

      • 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.

        • Bad research is still bad. The main paper is 9 pages with wide margins, outside of references. This was a few college students publishing their CS research assignment. The “Limitations” section is rather telling:

          Another interesting avenue opened by this work is how to improve the automatic generation of useful context files.

          Okay, so they already admitted that they started with useless context files, which sabotages their own test.

          You know how you fix useless context files? You iterate until they are useful context files!

          This whole research paper is XKCD 385, except with AGENTS.md files.

          • I haven’t read the paper in dept, but these are deeply unserious reasons for disparaging it.

            Bad research is still bad. The main paper is 9 pages with wide margins, outside of references. This was a few college students publishing their CS research assignment

            The length of this paper entirely within the norm for scientific publications. In fact, depending on the type of paper, they can be much shorter. For example, Nature expects submissions at around 2500 words or around 4300 words, depending on the format, while this paper is around 4800 words long (excluding references and SI).

            The authors also obviously not “a few college students publishing their CS research assignment”: Gloaguen, Mündler, Raychev, Müller, and Vechev.

            The “Limitations” section is rather telling:

            Another interesting avenue opened by this work is how to improve the automatic generation of useful context files.

            Okay, so they already admitted that they started with useless context files, which sabotages their own test.

            You know how you fix useless context files? You iterate until they are useful context files!

            The entire point of the study was to see what kind of context files were useful and which were useless, which according to the authors was not something that had been done before:

            A widespread practice in software development is to tailor coding agents to repositories using context files, such as AGENTS.md. Although this practice is strongly encouraged by agent developers, there is currently no rigorous investigation into whether such context files are actually effective for real-world tasks. In this work, we study this question and evaluate coding agents’ task completion performance in two complementary settings

            They found that,

            while instructions in the context files are well followed by coding agents, repository overviews, although popular and recommended by model providers, are not helpful.

            So when you say that they “admitted that they started with useless context files”, you are referring to the results of the study. Complaining that they didn’t base their study on the conclusions of that very study is just absurd

      • Ai is shit because of the people behind it, and because of the crypto bro mentality of its users.

        • Please add the cost : this is not for everyone, not even close. Investor are paying for 99% of the cost right now with the hope of having everyone dependent on the tools to then multiply the prices by 100 once the “market penetration” feels satisfactory.

          Also purely stealing people’s jobs from those same people’s work even when the work is explicit stating they refuse to be part of this farce.

          • Environmental costs, and the already recorded lower education scores as well.

            ai was something that always seemed like a requirement for the future, but has now become the thing most likely to stop there being a future.