footfaults

Interesting. I wonder if this is a beginning of a climb down for the Very Serious People so that we can eventually make a peace deal.

Gell-Mann Amnesia effect

Witchcraft

Average American moment

Don't know what to tell you. Been doing it that way since 2011

Not exactly, because n commits will have been squashed into one, so making the edit would lose the reference to the originals which should have been squashed with other commits

See but you can break the commit back apart by doing a git rebase interactive, selecting that squashed commit as the commit to edit, then doing a git reset HEAD~1 then recommit it in pieces, then git rebase --continue

Then git rebase -i a second time and then remove the commit that you don't want to be included

If you are continually rebasing and having to fix the same merge conflict over and over, you should look at https://git-scm.com/book/en/v2/Git-Tools-Rerere

You can also do a git rebase -i and mark a commit as edit and git will stop at that commit in the rebase to allow you to stop, look around, and make changes.. I think that is what you are looking for

I want to say that you've piqued my interest, but honestly I'm not sure I can set aside my bias. I deal with enough wrong code already as it is that my co-workers write, so I don't know if having yet another one giving me bad code suggestions adds much, but I appreciate you putting in the work showing everything.

very true

ok first dumb question, is the block of code that you had below this line

Given a query of “write a json schema to represent a comment thread on a social media site like reddit”, it’ll do this bit of reasoning:

Was this an actual output from an LLM or a hypothetical example that you wrote up? It's not quite clear to me. It's a lot of output but I don't want to insult you if you wrote all that yourself

First, each comment has an ID, author info, content, timestamps, votes, and replies. The replies are nested comments, forming a tree structure. So the schema should allow for nested objects within each comment's replies.

I ask because I really want to nitpick the hell out of this design decision:

First, each comment has an ID, author info, content, timestamps, votes, and replies. The replies are nested comments, forming a tree structure. So the schema should allow for nested objects within each comment's replies.

Adding the replies as full items, that is going to absolutely murder performance. A better scheme would be for replies to be a list/array of IDs or URLs, or a URL to an API call that enumerates all the replies, instead of enumerating all the items and embedding them directly. That is going to absolutely kill performance. Depending on the implementation, you could easily be doing the classic N+1 query that a lot of web applications fall for.

But then again at this point I'm arguing with an LLM which is generating absolutely dogshit code.

I mean yes you are right on those points, it's just that this ridiculous policy used to follow the following criteria

However that seems to be no longer the case, at least when it comes to Ukraine

simultaneously weak, and strong