Ask HN: AI Code Smells
1–10 of 11 posts
Re: Ask HN: AI Code Smells
#2Re: Ask HN: AI Code Smells
#3Think twice; don't feed the beast.
Re: Ask HN: AI Code Smells
#4- Backwards compatibility, "This way handles version X, which end-of-life was 10 years ago."
- Unit tests with too much overlap. "Should add positive nums, Adds neg nums, Adds zero, …"
Re: Ask HN: AI Code Smells
#5While I'm sure this question is being asked in good faith, and this site is certainly the place for discussion regarding such matters, anyone replying might want to consider that you are assiting both sides in the development of this tech by pointing out it's identifying features. All clues to how LLMs generate and display output can then be better hidden from their next iteration. Think twice; don't feed the beast.
Re: Ask HN: AI Code Smells
#6Re: Ask HN: AI Code Smells
#7Re: Ask HN: AI Code Smells
#8Tests that are not connected to anything. You'll have FooTest but it's all mocks, never connect to Foo. My favorite was something like Assert('this function is able to destroy a planet') which returns true as just because it asserted a string.
Comments as signboards where to go next.
Really specific comments like `Alice function has been moved to RepositoryAlice`. Especially things that nobody would ever ask about.
Re: Ask HN: AI Code Smells
#9Who gives a shit?
If it works it works.