5 exercises on saying version numbers, decimals and units aloud.
0 / 5 completed
1 / 5
How do you read the version number "v2.3.1" aloud?
A semantic version like v2.3.1 is read by saying each number separately with "point" for each dot: "vee two point three point one". The "v" is read "vee" (for "version"), and the dots are not decimal points — they separate major, minor and patch numbers. So you never say "two point thirty-one" or "two thousand three hundred". Each segment is its own number: "two", "three", "one". For "v1.0.0" you say "vee one point oh point oh" (or "version one point zero point zero").
2 / 5
How is the decimal number "3.14" (as in pi) read aloud?
A genuine decimal number like 3.14 is read with "point" followed by each digit individually: "three point one four". After a decimal point, you say the digits one at a time ("one", "four"), NOT as a whole number ("fourteen"). So 3.14159 is "three point one four one five nine". This differs from version numbers only in that there is a single decimal point. Contrast: the version "3.14" (if it were a version) would also be "three point one four" — but a release like "v3.14.2" is "three point fourteen point two"? No — version segments are whole numbers, so it is "three point one-four"? Standard practice reads version segments as whole numbers: "v3.14.2" = "vee three point fourteen point two". For the math constant, digits are read singly: "three point one four".
3 / 5
How is the architecture name "x86_64" typically read aloud?
The CPU architecture x86_64 is read "ex eighty-six sixty-four". The "x" is the letter "ex"; "86" is read as the whole number "eighty-six"; "64" as "sixty-four". The underscore is usually not spoken (or, if you must, "underscore"). It is the 64-bit extension of the x86 family, also written "amd64" ("AMD sixty-four") or just "x64" ("ex sixty-four"). So "build for x86_64" is "build for ex eighty-six sixty-four". Avoid reading the digits singly ("eight six six four").
4 / 5
How should you read the IP-style or version segment in "v10.0" — is the "10" read "ten" or "one-oh"?
Within a version number, each segment is read as a whole number. So v10.0 is "vee ten point oh" (or "version ten point zero") — the "10" is "ten", not "one-oh". Similarly "v2.10.0" is "vee two point ten point oh" (note: "2.10" comes after "2.9" in semantic versioning — it is "two point ten", a higher minor version than "two point nine"). The "point" separates segments; the digits within a segment combine into a normal number. Zero is read "oh" or "zero".
5 / 5
How do you read a measurement like "16GB" or a rate like "100ms" aloud?
Metrics are read as the number plus the full unit name: 16GB is "sixteen gigabytes" and 100ms is "one hundred milliseconds". The number is a normal whole number ("sixteen", "one hundred"), and the unit abbreviation is expanded: GB = "gigabytes", MB = "megabytes", ms = "milliseconds", µs = "microseconds", Hz = "hertz". So "8GB of RAM" is "eight gigabytes of ram", and "a 50ms latency" is "a fifty-millisecond latency". You normally do not spell out the unit letters ("G-B"); you say the word. Be careful: "ms" is milliseconds, "µs"/"us" is microseconds.