3 ms·
> the other doesn't have any tradeoffs, it's just a better way of doing things based on novel techniques At least in the case of code, this isn't true. The var
by brundolf 6y ago
> the other doesn't have any tradeoffs, it's just a better way of doing things based on novel techniques
At least in the case of code, this isn't true. The variability comes in terms of change to the system, rather than the running of the system. i.e., if I simplify a process to be less modular and more monolithic, making it more efficient, that also makes it more purpose-built and less flexible. The "risk" increases of running up against a change that needs to be made but is intractably onerous. There's always a tradeoff.
- Jtsummers 6y agoI posted this in a similar thread yesterday: > Fisher's Fundamental Theorem: The better adapted a system is to a particular environment, the less adaptable it is to new environments. -- Gerald Weinberg,"The Psychology of Computer Programming" It's something everyone should consider in making critical design decisions. Your adaptable, modular system has some risks (particularly in terms of meeting performance targets, increased cost due to increased complexity), but the monolithic system has its own risks (less adaptable to changing requirements, potentially more fragile against attack or damage). Which you choose depends on many variables including your risk profile and anticipated need for change in the future.
- dllthomas 6y agoIMO, it seems like there's always a tradeoff once we've restricted ourselves to interesting options, because those options are interesting because they're not obviously dominated by other options. If we consider any possible solution, we can obviously imagine adding a completely spurious detail.
- brundolf 6y agoThat's fair