Good coding style

A good programming style makes money.[¹]

Good coding style is measurable but hard to apply daily. Code is pragmatic; it should support a business. Good coding style can be measured by the total amount of revenue it produces.

There should be no code in your application for anticipatory reasons. You cannot guess the future. You will always be wrong, and when you add complexity to the code-base to do a thing that you think will live in the future, it will always cost you money, the opposite of a good coding style.

–

[¹]: Kent Beck(1997): Smalltalk best practice patterns(https://www.amazon.com/Smalltalk-Best-Practice-Patterns-Kent/dp/013476904X)