The problem isn’t what the article author believes, but rather what developers commonly (perhaps almost universally) believe.
Most developers will fall back to intuition for any performance oriented decision even when they otherwise prefer data oriented decisions and even when the task at hand is critical to the health of their product/business. This is because performance measures require:
1. Additional effort
2. (most importantly) A willingness to abandon familiar concepts of approach
Sometimes such decisions vested in intuition are truth by omission, a form of lying, because the resulting self-comfort is worth more than the numeric benefits.
Most developers will fall back to intuition for any performance oriented decision even when they otherwise prefer data oriented decisions and even when the task at hand is critical to the health of their product/business. This is because performance measures require:
1. Additional effort
2. (most importantly) A willingness to abandon familiar concepts of approach
Sometimes such decisions vested in intuition are truth by omission, a form of lying, because the resulting self-comfort is worth more than the numeric benefits.