Sometimes the solution is 99% correct but the other 1% is so subtly wrong that it both doesn't work and is a debugging hell.

Welcome to programming.

I think the parents post happened to everybody, and if it hasn’t it will.

The edge between being actually more productive or just “pretend productive” using large language models is something that we all haven’t completely figured out yet.

often it's something you casually overlook, some minor implementation detail that you didn't give much thought to that ends up being a huge mess later on, IME

Ya but you kind of get painted in corner sometimes. And sunken cost fallacy kicks in.

It's on you however for not understanding the greater point?