I actually got really clean, well commented code from Copilot earlier this week.

I have no experience with JavaScript to speak of, but realized a Bookmarklet would be a perfect solution for reformatting a particular web app for printing. I already had a head replacement with CSS to do all the formatting, and I was using a RegEx to strip all script tags.

Anyway, I asked Copilot to write the Bookmarklet to replace the header, with full contents explaining the training behind the code, and an explanation of how the script functions below. When I got an error, I asked if to fix the error and or identified that Bookmarklets work better as single lines, so it fixed it. Then I added the requirement about replacing scripts, and it did that too, but for commented and a clean one-line version.

The one-live versions even up getting truncated, so I need to copy/paste from earlier (correct) endings, but otherwise it was an incredibly smooth experience.

I spent longer writing the guide for how to use it than the time it took to vibe code it and test it. I was super impressed.

(Granted, that's a pretty easy coding task...)

I once tried vibe coding a web app using GitHub Copilot. That motherfucker wrapped every single endpoint with

try:
    ...
except Exception:
    return "An error occurred"

What the fuck is wrong with you Copilot? This piece of shit trying to hide all the errors. If I don't know there are errors then there aren't errors. Apparently

Proper comments describe why... For example say you are using an api which requires guids and your application doesn't care are collisions as much so just use int id's.

You could add in a comment like

// creating a guid to interface with special api.

But just saying

// generate guid

Means nothing, your method should be generate_guid() or GenerateGuid(). Your comment is repeating.

Or this is probably going to hit my last company at some point, there was a system to read a serial number. They also wanted a "status" on the screen to verify the system was connected and running properly but both these values came over same signal wire. Depending on your exact ms timing sometimes you would read the status as the serial number. Another programmer wrote a check to verify the serial number did not start with OK. The comment added was

// add on 11/15/23 by Initials

With no other details. The serial numbers were 8 numeric digits. Someone won't know the history and delete this seemingly useless check and cause a 10s of 1000s of dollars in loss