Practice the English phrases used for expressing magnitude, scale, and rough approximations in technical conversations: orders of magnitude, rough estimates, and ballpark language.
0 / 8 completed
1 / 8
What does 'ballpark figure' mean in an estimation context?
A ballpark figure is an informal rough estimate. 'Can you give me a ballpark on the effort?' means: give me a rough number, not a precise commitment. It signals that precision is not expected.
2 / 8
What does 'order of magnitude' mean?
Orders of magnitude are used for rough scale comparisons: 1,000 users vs 10,000 users is one order of magnitude. It is faster to say 'this is two orders of magnitude slower' than to list exact numbers.
3 / 8
Which phrase expresses appropriate uncertainty in a rough system design estimate?
Good approximation language gives a range, states the assumption it depends on (traffic), and explains what would be needed for greater precision. This is more useful than refusing to estimate.
4 / 8
What does 'rough order of magnitude' (ROM) estimate mean in project planning?
ROM estimates are early-stage approximations with wide error bars. Stakeholders requesting a ROM understand they will get a range, not a commitment. The accuracy improves as requirements are defined.
5 / 8
How would you communicate scale when describing database storage needs?
Back-of-envelope calculations show your reasoning: data per record × users × growth rate. This lets colleagues check your assumptions and correct them. The final numbers guide infrastructure decisions.
6 / 8
What does 'within an order of magnitude' mean when comparing systems?
Within an order of magnitude means the numbers are in the same ballpark — not 100x or 1000x apart. 'Your solution and mine are within an order of magnitude in cost' means they are comparable, not vastly different.
7 / 8
Which of these is the best approximation phrase for a system design discussion?
Good estimation starts with a stated assumption (100 req/sec as a baseline), explains the reasoning, and acknowledges it will be updated with real data. Stating 'design for infinite scale' is a classic over-engineering anti-pattern.
8 / 8
How do you use 'roughly', 'approximately', 'around', and 'in the region of' correctly?
Register matters: 'roughly' and 'around' work in Slack and meetings; 'approximately' suits documents and presentations. 'In the region of' (British English) is formal and precise-sounding. All are grammatically correct in technical English.