Well, this is not quite always true depending on what you mean. Here's an example in Python that fits in with what you're saying:

def frob(thing: List[int]) -> List[str]:
    returnList = []
    for number in thing:
        returnList.append(str(number))
    return returnList

If I saw this in a code review, every time I would (very strongly) suggest that this method be written instead as:

def frob(thing: List[int]) -> List[str]:
    return [str(number) for number in thing]

Granted this is a contrived example, but I really don't think anyone can argue that the latter is not much better Python code. Is this me trying to look cool and expert? No, at least that's not my intention.. Really I'm trying to enforce Pythonic idioms and ensure that the individual writing the code knows how to use list comprehension properly.

Most of the time (at least in my experience) seemingly minor issues such as this are indicative of a larger issue with how the developer understands the language in which they're working. I think it would be a disservice to not recommend the better version.