So I had a huge refactor and thought "Ok, this should be right up GenAI alley". And in fact took your very approach of giving an example for a few and said "go at it".

To my surprise, it actually did it pretty poorly, would not work, when it would have worked, dire performance implications. Failing to address things that technically would survive the rework functionally intact, but now a very bad way of doing things in new context. Problems exacerbated is that when I'm reviewing code, I tend to have a more optimistic assumption of the code than when I'm writing and second guessing myself. So it's all the more annoying to read code I didn't write screw up so much.

I will say it does a pretty good job of boilerplate heavy crap. If I'm going to want to make Go structs from JSON, I can just feed a sample and the very tedious work of making the sometimes maddening tedius Go structs gets chewed through pretty nicely.

[–] Zarobi@aussie.zone 0 points 5 hours ago

Yeah I once tried to use it to write complex SQL and it just completely sucked at it. Like insanely inefficient queries that scan multiple tables multiple times instead of more efficient joins and other methods… Shame, I was hoping it would be good for refactoring at least if you gave it good examples