1 / 5
Caching computed results to save CPU at the cost of RAM is a classic ___ trade-off.
-
-
-
-
The space–time trade-off: you spend memory (storing results) to save time (recomputation), or vice versa.
2 / 5
Optimising code before profiling shows it matters is called ___ optimisation.
-
-
-
-
Premature optimisation wastes effort and often harms readability for gains that don't matter; measure first to find the real bottleneck.
3 / 5
Which phrase argues against a risky micro-optimisation?
-
-
-
-
Weighing a tiny speed gain against a large maintainability cost is exactly the trade-off conversation good engineers have.
4 / 5
The principle 'measure, don't guess' means you should ___ before optimising.
-
-
-
-
Profiling reveals where time is actually spent, so effort targets the real hot path rather than assumptions.
5 / 5
Spending engineering time where it yields the biggest user-facing win reflects optimising for ___.
-
-
-
-
Prioritising by impact ensures limited optimisation effort improves what users actually feel, not just impressive-looking numbers.