did it detect n+1 in the first one, race condition in the second one and memory leak in the third one?

It did, yeah.

Could it be that it just found this article and suggested issues based on that? Because the issues are somewhat arbitrary. One could make a case for a several different issues for any of the snippets and yet the model chose the exact ones mentioned by the article.

from the article :)

> if Susan is unavailable for cross-examination, the answer is hearsay

completely agree with the article

it is astounding how quickly people drop all reasoning before what is essentially a very cool party trick and instantly start believing in magic

not saying agi will never happen but i don't see it happening through llms

That's neat! On that note I've been using S3 as a private registry for years now via Gitlab and couldn't be happier!

I couldn't agree more!

i've been doing it for years with zero issues, took like 10 minutes to set up

> which is kinda unsurprising since it has no body, no world, no space; it "lives" in the realm of text

or rather the training set was lacking in this regard

this is an interesting statement, are you involved in LLM research?

where did you get the glasses from?

They're GloFX, the rose coloured ones. Got them from eBay. They do all the irlen colours under the guise of colour therapy.

you can always use views + triggers for a zero downtime migration, this is a non-issue

It sounds like gh-ost is supposed to offer more control over the process but I question how many companies need that level of sophistication in DB migrations.

Can you expand on this? I'm curious about the steps.

Sounds like it's basically explained in the gh-ost readme https://github.com/github/gh-ost#how

I think it amounts to "use views to decouple access to the table with a fixed interface" and "use triggers for migrating data between tables"