* Space vs. Speed
- Most famous one. (Memory space vs. execution speed) - details are omitted.
* Modularity vs. (Performance & Space)
- Well-designed-module should be stable. To be stable, there may be lots of 'parameter check', 'condition check', 'sanity check' and so on. Besides, for the safety reason, it may not trust passed memory space. So, it may allocates it's own memory space and try to copy data from passed memory to use it. Those make this trade-off. Well-designed-module hides it's information and stable as it is. But to be like this, it consumes speed and space.
* Abstraction vs. Debugging
- When software is stable, abstraction reduces maintenance costs very much. But, if not, debugging is more difficult than straightforward designed software, especially, to the engineer who are not accustomed to the software.
* low possibility to misuse vs. various and rich functionality
- It is clear...
* Backward-Compatibility vs. Innovation
|[Dev] one persone under full responsibility for one time-critical-project (0)||2009.01.21|
|[Prog] What is "good code"? (0)||2008.11.22|
|[Prog] Trade offs (0)||2008.05.12|
|[Prog] Avoid prematured exception handling... (0)||2008.04.27|
|[Prog] Outputs should be separated from inputs at directory level. (0)||2008.02.19|
|[Dev] Let's make schedule-history-table! (0)||2007.11.25|