I disagree on principle. Readability is not even close to the top of the list of why I want the code running on my systems to be "clean". Clean software demonstrates good faith by the developers and a competent, ground up understanding of the problem I am trying to tackle by running your software. Clean, to me, means the code is generally not doing more than it has to, resulting in lower attack surface, better performance, lower power usage and thus less environmental impact at scale, and just a tighter, more sensible, reasonable, easy to understand user experience. Maybe this doesn't matter much at your job, which seems to be where they're trying to replace people with these parrots, but it matters a lot on your computer, and it matters even more the other three billion computers.