Feature Development vs. Structural Changes

A central problem in software design is finding a balance between structural and behavioral changes.

The salient point is that we either change the system’s behavior or structure, but never both simultaneously. These changes compete for resources.

Every behavior change is a potential source of cash, either through higher revenue or lower costs.

Structural changes are never a direct source of revenue. Structural changes should increase optionality.

If “feature development = revenue” & “structural changes = option,” then the struggle for balance makes more sense. It’s not about the personalities of Product versus Engineering.

The struggle is economic — do we make some money now or more money later? The answer is always “both.” It’s about more than short-sighted versus visionary thinking.

We have to make some money now to survive. We want to make “more” money later through options.