▲ | nottorp 17 hours ago | ||||||||||||||||||||||
So, most low level functions that enumerate the files in a directory return a structure that contains the file data from each file. Including size. You already have it in memory. Your brilliant AI calls another low level function to get the file size on the file name. (also did worse stuff but let's not go into details). Do you call reading the file size from the in memory structure that you already have a speed optimization? I call it common sense. | |||||||||||||||||||||||
▲ | miningape 15 hours ago | parent [-] | ||||||||||||||||||||||
Yep exactly, LLMs blunder over the most simple nonsense and just leaves a mess in their wake. This isn't a mistake you could make if you actually understood what the library is doing / is returning. It's so funny how these AI bros make excuse after excuse for glaring issues rather than just accept AI doesn't actually understand what it's doing (not even considering it's faster to just write good quality code on the first try). | |||||||||||||||||||||||
|