55
It ensures that the agent does a good job (lemmy.world)
submitted 5 months ago by to c/fuck_ai@lemmy.world
7 comments fedilink hide all child comments
 

Image Text:

Github overview of a pull request for the file AGENTS.md.

Comments regarding line "# Repository Guidelines" in the file:

zanieb: "What's the point of this title? Seems like wasted tokens?"

zanieb: "(certainly inconsequential in the big scheme, but I don't see it adding value)"

charliemarsh: "It ensures that the agent does a good job."

all 7 comments

sorted by: hot top controversial new old
[–] 17 points 5 months ago* (1 child)

I’m proud of the fact that I don’t understand this.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    • [–] 13 points 5 months ago (2 children)

    It wastes tokens which is good. Every penny my boss spends on AI brings the company closer to bankruptcy.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
    • [–] 4 points 5 months ago (1 child)

    If the agent can't tell a contextual comment from an actionable code line, then it is indeed a wasted token. Not because of the header, but because of the "AI" being a useless POS.

    Which, to be fair, is the case in pretty much all scenarios.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    • 18 comments in c/programmer_humor@programming.dev view that post
    [–] 78 points 5 months ago (13 children)

    Everyone knows you have to tell it "don't make mistakes".

  • permalink
  • fedilink
  • source
  • hideshow 13 child comments
    •
  • [–] 47 points 5 months ago (10 children)

    "DO NOT HALLUCINATE"

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 15 points 5 months ago (5 children)

    Ahh, the "git gud" gamer hack also applies to sloperations? Good to know!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 6 points 5 months ago (3 children)

    git config —global alias.gud “reset —hard @{upstream}”

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 5 months ago (1 child)

    You are a monster. Nice work!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 5 points 5 months ago

    Ah, went and checked my work laptop this morning. It’s actually set to: !”git reset —hard HEAD && git clean -fdx

    git it is the one that’s set to upstream.

    I also have git some: add -p, git away: checkout -p, git out: !”git merge —abort 2> /dev/null || git rebase —abort 2> /dev/null #”

    And some complicated ones I’m not gonna type on my phone:

    • git on <foo> where foo is either “it”, in which case I use the appropriate main/master/develop branch and rebase on it; or foo is “up” in which case I do a pull —rebase and play a short audio clip of Get On Up; or foo is a nonexistent branch, in which case I massage the requested branch name to adhere to some conventions and then make a new branch and set the remote tracking branch
    • git with <foo> where the same “it” logic applies but it’s a merge; or foo is a commit SHA and it gets cherry-picked
    • git up is just a pull but it plays a short audio clip of Get On Up
    • I think I had a git rekt at one point, but I think it just did the same as git gud so I deleted it
  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 5 months ago 
    git config --global alias.lsd '!f(){ p(){ awk '\''BEGIN{srand()}{a[NR]=$0}END{print a[int(rand()*NR)+1]}'\''; }; git reset --hard -q; git clean -fdq; if [ "$(awk '\''BEGIN{srand();print int(rand()*2)}'\'')" = 0 ]; then c=$(git rev-list --first-parent HEAD|sed "$d"|p); git reset --hard "$(git rev-parse "$c^")"; else c=$(git rev-list --all|grep -v "^$(git rev-parse HEAD)$"|p); git reset --hard "$(git commit-tree "$c^{tree}" -p HEAD -C "$c")"; fi; }; f'

    You're welcome.

  • permalink
  • fedilink
  • source
  • parent
    • [–] 38 points 5 months ago* (last edited 5 months ago)

    that's just good form, regardless of who's reading the md

    • MD041 - First line in a file should be a top-level heading
    • MD002 - First header should be a h1 header
    • MD025 - Multiple top level headers in the same document

    that whole line is 3 tokens btw, they're wasting more time and energy just discussing that

  • permalink
  • fedilink
  • source
    •
    [–] 3 points 5 months ago

    Without this, we wouldn't be sure the agent does a good job!

  • permalink
  • fedilink
  • source
    •
    [–] 2 points 5 months ago

    damn, Charlie really fell off

  • permalink
  • fedilink
  • source
    •