Am I not being to(o) explicit?

Names are not too explicit, but verbose.

Consider using standard physical units with metric units as the default: "meter, second, Volts, Amps, ...".

Example, for speed, use all speed data in meters/second (unless otherwise name/commented). Then the names can be shorter.

// const int speedOfSoundInAirInMetersPerSecond = 343;
const int speedOfSoundInAir = 343 /* m/s */

Rather than ratios, use "per" or "p". Use standard SI abbreviations. For non-SI units, use the word like "inch". Use float constants for float objects.

// const float centimeterToInchRatio = 2.54;
const float cm_per_inch = 2.54f;

As able, object name should primarily reflect what they are and then maybe, and secondarily, units. Notice how easy it is to read and see the units balance.

// cm = (speedOfSoundInAirInCentimeterPerMicrosecond / 2) *  readTravelTimeInMicroseconds(7, 7);
int distance_cm = (speedOfSoundInAir_cm_per_us * readTravelTime_us(7, 7))/2;

// inches = (cm / centimeterToInchRatio);
int distance_inch = distance_cm * inch_per_cm;

Note that OP's speedOfSoundInAirInCentimeterPerMicrosecond / 2 effectively lost the last bit of the speed.

When working with small computing machines and processing time is important, consider the impact of FP math vs. an all int solution. Code may gain performance, but watch out for overflow.

const float inch_per_cm = 2.54f; /* inch / cm */
int distance_inch = distance_cm * inch_per_cm;

// vs all int solution
const int inch_per_cm_N = 254; /* inch / cm */
const int inch_per_cm_D = 100;
// Round by adding half denominator (assuming pos values)
int distance_inch = (distance_cm*inch_per_cm_N + inch_per_cm_D/2)/inch_per_cm_D;

Am I not being to(o) explicit?

Names are not too explicit, but verbose.

Consider using standard physical units with metric units as the default: "meter, second, Volts, Amps, ...".

Example, for speed, use all speed data in meters/second (unless otherwise name/commented). Then the names can be shorter.

// const int speedOfSoundInAirInMetersPerSecond = 343;
const int speedOfSoundInAir = 343 /* m/s */

Rather than ratios, use "per" or "p". Use standard SI abbreviations^*1. For non-SI units, use the word like "inch". Use float constants for float objects - append an f.

// const float centimeterToInchRatio = 2.54;
const float cm_per_inch = 2.54f;

As able, object names should primarily reflect what they are and then maybe, and secondarily, units. Notice how easy it is to read and see the units balance.

// cm = (speedOfSoundInAirInCentimeterPerMicrosecond / 2) *  readTravelTimeInMicroseconds(7, 7);
int distance_cm = (speedOfSoundInAir_cm_per_us * readTravelTime_us(7, 7))/2;

// inches = (cm / centimeterToInchRatio);
int distance_inch = distance_cm * inch_per_cm;

Note that OP's speedOfSoundInAirInCentimeterPerMicrosecond / 2 effectively lost the last bit of the speed.

When working with small computing machines and processing time is important, consider the impact of FP math vs. an all int solution. Code may gain performance, yet watch out for overflow.

const float inch_per_cm = 2.54f; /* inch / cm */
int distance_inch = distance_cm * inch_per_cm;

// vs all int solution
const int inch_per_cm_N = 254; /* inch / cm */
const int inch_per_cm_D = 100;
// Round by adding half denominator (assuming pos values)
int distance_inch = (distance_cm*inch_per_cm_N + inch_per_cm_D/2)/inch_per_cm_D;

^*1 Using u for μ.

Am I not being to explicit?

Consider using standard physical units with metric units as the default. "meter, second, ..."

Example, for speed, use all speed data in meters/second (unless otherwise name/commented). Then the names can be shorter.

// const int speedOfSoundInAirInMetersPerSecond = 343;
const int speedOfSoundInAir = 343 /* m/s */

Rather than ratios, use "per". Use standard SI abbreviations. Use float constants for float objects.

// const float centimeterToInchRatio = 2.54;
const float cm_per_inch = 2.54f;

As able, object name should primarily reflect what they are and then maybe, and secondarily, units. Notice how easy it is to read and see the units balance.

// cm = (speedOfSoundInAirInCentimeterPerMicrosecond / 2) *  readTravelTimeInMicroseconds(7, 7);
int distance_cm = (speedOfSoundInAir_cm_per_us * readTravelTime_us(7, 7))/2;
 

// inches = (cm / centimeterToInchRatio);
int distance_inch = distance_cm * inch_per_cm;

Note that OP's speedOfSoundInAirInCentimeterPerMicrosecond / 2 effectively lost the last bit of the speed.

When working with small computing machines and processing time is important, consider the impact of FP math vs. an all int solution. Code may gain performance, but watch out for overflow.

const float inch_per_cm = 2.54f; /* inch / cm */
int distance_inch = distance_cm * inch_per_cm;

// vs all int solution
const int inch_per_cm_N = 254; /* inch / cm */
const int inch_per_cm_D = 100;
// Round by adding half denominator (assuming pos values)
int distance_inch = (distance_cm*inch_per_cm_N + inch_per_cm_D/2)/inch_per_cm_D;

Am I not being to(o) explicit?

Names are not too explicit, but verbose.

Consider using standard physical units with metric units as the default: "meter, second, Volts, Amps, ...".

Example, for speed, use all speed data in meters/second (unless otherwise name/commented). Then the names can be shorter.

// const int speedOfSoundInAirInMetersPerSecond = 343;
const int speedOfSoundInAir = 343 /* m/s */

Rather than ratios, use "per" or "p". Use standard SI abbreviations. For non-SI units, use the word like "inch". Use float constants for float objects.

// const float centimeterToInchRatio = 2.54;
const float cm_per_inch = 2.54f;

As able, object name should primarily reflect what they are and then maybe, and secondarily, units. Notice how easy it is to read and see the units balance.

// cm = (speedOfSoundInAirInCentimeterPerMicrosecond / 2) *  readTravelTimeInMicroseconds(7, 7);
int distance_cm = (speedOfSoundInAir_cm_per_us * readTravelTime_us(7, 7))/2;

// inches = (cm / centimeterToInchRatio);
int distance_inch = distance_cm * inch_per_cm;

Note that OP's speedOfSoundInAirInCentimeterPerMicrosecond / 2 effectively lost the last bit of the speed.

When working with small computing machines and processing time is important, consider the impact of FP math vs. an all int solution. Code may gain performance, but watch out for overflow.

const float inch_per_cm = 2.54f; /* inch / cm */
int distance_inch = distance_cm * inch_per_cm;

// vs all int solution
const int inch_per_cm_N = 254; /* inch / cm */
const int inch_per_cm_D = 100;
// Round by adding half denominator (assuming pos values)
int distance_inch = (distance_cm*inch_per_cm_N + inch_per_cm_D/2)/inch_per_cm_D;