Re:The critical role of systems thinking in software develop...
by fulafel on Tuesday September 06, 2016 @01:01AM
(#12433761)
I think 1 and 3 are pretty practical, and you can get part way to 2. Appreciation of simplicity, transparency, robustness etc can be good inputs to your design without crippling it. There are lots of situations where there is a better practical solution but you just stop looking for it because you don't have a reason to say "not good enough" to the inferior solution.
[ Parent
| on HN ]
Re:The critical role of systems thinking in software develop...
by jdale27 on Tuesday September 06, 2016 @01:21AM
(#12433807)
1 and 3, however, are in conflict.
As Tony Hoare said, there are two ways to write software: one is to make it so simple that there are obviously no bugs; the other is to make it so complicated that there are no obvious bugs. Clearly the former is much more difficult and expensive; hence in practice (again, except in those critical domains) we end up doing the latter, because the economic incentive to do the former just isn't there, even if we know the customer (and we as developers) would be happier with it.