216

Time to look for a new line of work... (programming.dev)

submitted 1 month ago by Cruel@programming.dev to c/programmer_humor@programming.dev

12 comments fedilink hide all child comments

Peak Gemini moment

top 12 comments

sorted by: hot top controversial new old

[-] thann@lemmy.dbzer0.com 39 points 1 month ago

// hire an actual programmer to fix this.

[-] four@lemmy.zip 36 points 1 month ago

Thank god it didn't do @eslint-ignore-error missing-property instead lol

[-] Cruel@programming.dev 10 points 1 month ago

My favorite is when it just removes erroneous code. Problem solved!

[-] joyjoy@lemmy.zip 6 points 1 month ago* (last edited 1 month ago)

// @ts-expect-error

[-] abbadon420@sh.itjust.works 21 points 1 month ago

What about //TODO ?

[-] goatinspace@feddit.org 16 points 1 month ago

└(・。・)┘

[-] PattyMcB@lemmy.world 10 points 1 month ago

Yeah...good luck, SkyNet. You're not quite there yet

[-] A_norny_mousse@feddit.org 6 points 1 month ago* (last edited 1 month ago)

~~I'm not sure what this is about, but~~ this looks like something my definitely not AI, hell not even a proper IDE, code editor with syntax highlighting could have flagged as well?

[-] qarbone@lemmy.world 21 points 1 month ago

Read the images top-to-bottom, left-to-right.

They used a shortcut to call the LLM to fix an error. The final "fix" was for the model to add a comment after the error saying "this is the error". It's about at the level of a real developer leaving a comment to themself saying "FIXME [later]", instead of just fixing it.

[-] A_norny_mousse@feddit.org 6 points 1 month ago

Thanks.

[-] Cruel@programming.dev 2 points 1 month ago

Yeah, the TS syntax highlighting already saw the problem, as it's underlined. I just tried to have it fix it real quick (it used Gemini Code Assistant's quick fix). Trying it a second time actually fixed it, fwiw.