I recovered the joy of programming. And I didn’t look back. I won’t pretend that number of lines of code or PRs is a valid metric, especially when AI can be as verbose as it wants to win on every metric. But I can say that I am pushing significant changes every day, getting PRs merged, and at the end of the day, getting the work done. And for that reason, I’m not scared of being fired. Plus, I’m keeping my brain functions intact.

  • Hugh@programming.dev
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    6 days ago

    This is similar to my experience. I have never used agents, but I have worked on projects with people who have. They could create PRs in a few hours that would take me half a week to fix.

    The agent would do things like create a new type definition in the same file as the function that used it. Except we already had a type definition in the types file so that it could be imported into different parts of the code.

    I try to employ “DRY” practices where applicable because it improves the readability, maintainability and extensibility of the code. A random word generator will never be able to understand things like the structure and architecture of the project, nor the project requirements, so it is liable to always increase technical debt.

    • Feyd@programming.dev
      link
      fedilink
      arrow-up
      8
      ·
      6 days ago

      This is similar to my experience. I have never used agents, but I have worked on projects with people who have. They could create PRs in a few hours that would take me half a week to fix.

      Isn’t it infuriating that they outsource work to you then get kudos because they’re telling the suits what they want to hear?

    • HaraldvonBlauzahn@feddit.orgOP
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      6 days ago

      The agent would do things like create a new type definition in the same file as the function that used it. Except we already had a type definition in the types file so that it could be imported into different parts of the code.

      Ouch. In C++, this violates the “One Definition Rule”, which will in this case likely not cause any compiler warning, and can cause extremely hard-to-find Undefined Behaviour bugs if, for example, the layout for classes or structs is different between definitions.

      (And the latter can of course easily happen if you later edit or extend one definition without being aware of redundant other definitions.)