One example for self documenting code is typing. If you use a language which enforces (or at least allows, as in Python 3.8+) strong typing and you use types pro actively, this is better than documentation, because it can be read and worked with by the compiler or interpreter. In contrast to documenting types, the compiler (or interpreter) will enforce that code meaning and type specification will not diverge. This includes explicitly marking parameters/arguments and return types as optional if they are.

I think no reasonable software developer should work without enforced type safety unless working with pure assembler languages. Any (higher) language which does not allow enforcing strong typing is terrible.

I have worked on larger older projects. The more comments you have, the larger the chance that code and comment diverge. Often, code is being changed/adapted/fixed, but the comments are not. If you read the comments then, your understanding of what the code does or should do gets wrong, leading you on a wrong path. This is why I prefer to have rather less comments. Most of the code is self a explanatory, if you properly name your variables, functions and whatever else you are working with.

This is the most French comment I read today

Nevertheless, 16% for a Nazi party is more than 16% too much.

Is that why mosquitoes prefer other people over me? 😉

There is a good old movie raising this question, among others: “The man from earth”

I guess they’ll leave you the ick.

Yeah, that’s a very useful exception.

Operator overloading is adding complexity, making code subtly harder to read. The most important lesson for code is: It should primarily be written to be easy to read by humans because if code is not trash, it will be read way more often than written.

Mostly minor improvement, such as the fossify phone app grouping by date in the call history

I’m avoiding the major search engines. If I really need a search engine, I use DuckDuckGo. Most of the time, search forms of a few websites provide better results. I’ve bookmarked search forms of e.g. wikipedia, Wiktionary, the python docs, Arch Linux wiki, github, dict.leo.org, bug trackers of software I commonly use (such as Mozilla’s bug tracker) and so on. I’m basically using Firefox’s “keyword” search feature in the way DuckDuckGo’s !bang syntax works.