Today's AI coding gripe: why does it insist (over and over, in languages that don't coerce types) that "'!(A > B)' can be simplified to 'A <= B'" when A and/or B is nullable? It keeps trying to make this change in C# and breaking code (further down, when calling A.Value but !A.HasValue)
Another complaint about any AI-generated code: what is it with all the try-catch? It's everywhere, and it never knows what to do with the caught exception. Best practice is to almost never use try-catch and have top level error logging baked into your app.
0 reposts4 likes