Programming in my world is about anticipating abstractions, without actually abstracting. We write code for it to be changed. We know to a certain extend how th

Programming in my world is about anticipating abstractions, without actually abstracting. We write code for it to be changed. We know to a certain extend how the specifications, design and code are likely to change over time. We anticipate the kind of abstractions needed to accommodate that change. This in turn influences the choice of programming language, unit testing, naming, modularization, infrastructure... Just as a simple counter example: I write my code so I minimize the amount of state and provide good type information. The advantage is that future (re-)composition in other abstractions of the code will continue to work.