As a non JS dev 15/28 by asking myself “what is the the most non-intuitive/inconsistent behaviour for this API to have?” ¯\(ツ)/¯

Kinda touches on the psychological aspect of this

A 1-indexed array to the head

I used to be a 110x high order vibe coder like you. Then I took an AIrrow to the knee.

I used to be a 110x high order vibe coder like you. Then I took an AIrrow to the knee.

Someday soon: Claude is down

Use pre-commit with a linter config that checks all files, local dev can have a different config to disable as needed.

The fun strings to enter in web forms once in a while.

I had another thought, added another one to the original reply.

I gave it a shot

Edit: I had another thought

Relevant xkcd

I don’t have any expertise or taken a look at it but this comment makes it so much worse: https://lemmy.ca/comment/16819736

This YouTube link at the time indicates part of the menu is. https://m.youtube.com/watch?v=kMJNEFHj8b8&t=276s

Depends what they want, if fixing gets more billable hours and that’s what the client wants so be it.

I can’t wait for the tide to turn so I can charge ridiculous consulting fees to fix shit.

We could see how the copilot PRs went:

BIGPISS Stack amazing

I mean this in the “humans shouldn’t be the only ones to suffer” way.

Sand should be forced to suffer too.

Well it’ll change the world by consuming a shit ton of electricity and using even more precious water to fill the data centres. So changing the world is correct in that regard.