> The criteria the developer is judged by will have nothing to do with the complexity of the software or the time it takes to create. Instead, their work will be judged and compensated by the value it delivers to the organization.
You say that like it's different, or should be, at a software company.
I disagree. I think that all work for an organization should be judged and compensated by the value said work delivers to said organization, regardless of the organization type, regardless of the work type.
> Even if it's crappy software.
Surely you're not suggesting that crappy software is always wrong/bad.
Good software is often more expensive than crappy software. That added expense doesn't necessarily produce more value.
Good programmers know that they're trying to maximize benefits-costs, not maximize the former, not minimize the latter.
You say that like it's different, or should be, at a software company.
I disagree. I think that all work for an organization should be judged and compensated by the value said work delivers to said organization, regardless of the organization type, regardless of the work type.
> Even if it's crappy software.
Surely you're not suggesting that crappy software is always wrong/bad.
Good software is often more expensive than crappy software. That added expense doesn't necessarily produce more value.
Good programmers know that they're trying to maximize benefits-costs, not maximize the former, not minimize the latter.
Worse can be better.