No it’s the single large commit of, not just the data, but the rest of the logic in conjunction with it. You did not appear to use any version control in the development of your app, yet you use it to maintain the app. That’s a AI “smell”.
As an aside, we used to use the term “code smell” back in the day when trying to trace the source of problems in an app. The “smell” would tend to lead you to the bad code.
It doesn’t guarantee this is purely AI generated. It’s just weird, and when held up to the rest of the git repos of the last two years, it gives the appearance of AI generated.
The “slop” part is debatably unfair still, but having an app be AI generated tends to mean little effort was put into the up front requirements analysis before a selection of functionality made.
Again, just generalizations on my part. If it makes you feel better, I’m working on an AI generated app to quantify the amount of times someone’s work is dismissed as “AI slop” so I can present a case to the moderation team to get the HN guidelines updated to discourage ONLY calling something slop without any evidence of it.
As an aside, we used to use the term “code smell” back in the day when trying to trace the source of problems in an app. The “smell” would tend to lead you to the bad code.
It doesn’t guarantee this is purely AI generated. It’s just weird, and when held up to the rest of the git repos of the last two years, it gives the appearance of AI generated.
The “slop” part is debatably unfair still, but having an app be AI generated tends to mean little effort was put into the up front requirements analysis before a selection of functionality made.
Again, just generalizations on my part. If it makes you feel better, I’m working on an AI generated app to quantify the amount of times someone’s work is dismissed as “AI slop” so I can present a case to the moderation team to get the HN guidelines updated to discourage ONLY calling something slop without any evidence of it.