As someone who's grown to be more familiar with programming in pure assembly, specifically x86/x64 and ARM, I've focused on the finer details in a variety of things. I've also learned that many common practices used in hacking/modding/cheating are simply due to existing tutorials and documentation that people blindly follow because they "work". One example I've always disliked were completed modding projects that used proxy DLLs to inject code, when an executable's file format already allows the ability to append sections, but it's easier for people to just copy an existing proxy DLL template, I suppose. I bring this point up as following the common practice isn't always the best or elegant idea. Over the years of analyzing assembly, you can start picking out various sections of code, understand the influence of the compiler, and interpret the coding practices the developers used and recreate their design practices while improving them. AI doesn't have this level of interpretation and will attempt to follow a common practice derived from an average of good and bad codebases.
AI generated tables are messy, convoluted, obscured, and can increasing the risk of malicious code, whether there's intent or not. I find AI generated tables to be distasteful and are flooding the pool of higher quality tables as well as the simpler ones that are indicative of a developers growth and insights, which can be used as examples by others to learn and improve. AI may provide "results", but these results are sloppy, primarily serve to prioritize quantity over quality, and ruin future maintainability, compounding its same flaws across the codebase. People try to wiggle out of this by saying they only use it as assistance, but if it's writing any piece of the code, I can't trust you, your code, or how much you claim to be using it for. If you really need a messy, generalized interpretation, analyze the AI code, but don't use it and don't push it out into production.
If AI generated tables become the norm, I'll just leave as I don't want my work mixed in with it.
"But, Geo, AI is here to stay, it's the future, and it's never going away!" Cool, do your thing, I just won't be a part of it.
"If you don't like AI code, why do you use [insert software here]?" I try to keep a keen eye for it and avoid it the best I can. Unfortunately I may need to settle with one begrudgingly, if I'm dependent on it. In the event this forum falls down the same path with its tables, I have no dependency to it.