In general, a good rule of thumb is only code "clean" enough so that you / your team / someone else can figure out what the hell you were doing at that particular area of the source code
_Clean Code_ is an extremely well-known book on programming by Robert “Uncle Bob” Martin from the 2000s. Posts about it have come up on HN as recently as this year.
Maybe it’s a sign of the times, but I’m surprised you’ve never come across it. I say this as someone who doesn’t agree with many of the suggestions.
The fact that he capitalized both Cs indicates he's talking about the book, which is famous enough that I learned about it and its influence when I was in school ~15 years ago.
GP wrote clean code (lowercase) which most people would take to mean the general practices of hygenic, well maintained code.
Clean code is over abstraction, spaghetti code. The people who are part of this cult just point to the source material and title, never critically think about why it might be bad (it’s super slow, check YouTube “clean code performance” for why) or entertain alternatives.
Because they can't.
Also, Clean Code is a really bad ideology, you should regret wasting time on it regardless of LLM code generation.