get into a rut early: do the same processes the same way. accumulate idioms. standardize. the only difference (!) between shakespeare and you was the size of his idiom list - not the size of his vocabulary.
an idiom is a memorable standardization of language which says something that could be said in multiple ways.
a programming idiom is a “design pattern” that fits in a few lines of code.
an idiom is a word in the meta-language.
a meta-language is spoken by the culture.
the goal of our meta-language is to describe a computer that is simple enough for a single human to understand.
the highest goal while building an idiom is to unbuild the system.
to construct in a way that sheds away the further construction of it/self.
to construct in a way that incorporates a new lesson, so that the system may be reborn.
in programming, as in everything else, to be in error is to be reborn.
no errors = no rebirth
correctness.
zero.
learning the language and idioms of your computer's construction lets you communicate with the community and the computer in a way that all three of you understand.
a shared language.
instead of simply having the machine learn our language, we learn the computer's language so that we may maintain our soveriegnty.
sovereignty necessitates understanding.
if you don't understand a system you're using, you don't control it.
if nobody understands the system, the system is in control.