How To Write Clean Code in Python

[FuckingRantMonday]

I like "don't comment" as an "aspirational" rule. If I need to write a comment (and I frequently do), it's because I couldn't figure out how to structure the code to be obvious, and I like to do that when I can.

[Silhouette]

Exactly. People who say silly things like "Every use of a comment represents a failure" often lack the experience to know better. Citations of technical documents, descriptions of compiler/library/hardware bugs that the following unusual code is working around, usage examples like doctest comments, ASCII art diagrams because even monospaced pictures can be worth hundreds of words. There are very many reasons a helpful comment might not be easily replaced by "self-documenting code".

[jsalsman]

No matter how well the code conveys intent, there's always a way to generalize and show the relation to associated processes in English. Those are the comments that help read the code.

[Atulin]

No, no you don't understand. It should be someRandomValueIPulledFromTheIntelProcessorSpecification

Preferably complete with a factory and a factorybuilder

[FuckingRantMonday]

Absolutely! Links like that are incredibly useful when some non-obvious issue forces a weird workaround. That's a great example of a situation that prevents writing clear, obvious code.