>>16
yeah, maybe later. It all depends on the ratio of (features / money). time = money / wage, and quality = time / features. So:
Let D be the ratio: features / money.
D = features / money
money * D = features
wage * time * D = features
wage * time * D = time / quality
wage * D = 1 / quality
quality * wage * D = 1
quality * wage = 1/D
So quality*wage is inversely related to features/money. If one quantity goes up, the other must go down.
Although having a quality code base saves an indefinite amount of time in the long run.
>>21
thanks man.