Why Base-60 Still Runs Your Clock

Add "1 hour 45 minutes" to "0 hours 30 minutes" and you don't get "1 hour 75 minutes" — you get "2 hours 15 minutes," because 60 minutes rolls over into the next hour the same way 10 ones roll over into the next ten in ordinary addition. The difference is the base: clocks count in 60s, not 10s, and that single fact is why time-duration math needs its own carrying logic instead of ordinary decimal addition.

Where base 60 actually comes from

The sexagesimal (base-60) system predates the Roman Empire by millennia — it's inherited from Babylonian mathematics, which used 60 as a base because it divides evenly by 2, 3, 4, 5, 6, 10, 12, 15, 20, and 30, far more divisors than 10 has. That made fractions easier to work with by hand long before decimal notation existed. The convention stuck for measuring angles and time specifically, while most everyday counting eventually settled on base 10 — so modern timekeeping is a live fossil of a 4,000-year-old number system, still running underneath every digital clock.

Why you can't just add the numbers like a decimal

Because minutes and seconds each cap at 60 (not 10), naive field-by-field decimal addition produces nonsense like "63 minutes." The fix is the same "carry" operation taught for decimal addition, just with a different threshold: sum the smallest unit, and every time it reaches 60, subtract 60 from it and add 1 to the next unit up. Seconds carry into minutes, minutes carry into hours, and — less commonly needed but just as real — hours carry into days once a duration exceeds 24 of them. Skipping this and just summing "hours," "minutes," and "seconds" as three independent decimal numbers is a common source of bugs in hand-rolled timesheet or stopwatch code, because it silently produces an unreadable result instead of erroring.

Subtraction has to borrow, not just carry

Subtracting durations hits the mirror-image problem: "2:00:00 minus 0:15:00" can't just subtract 15 from 0 minutes, because that goes negative. It has to borrow 60 minutes from the hours column first — turning 2:00:00 into 1:60:00 — before the subtraction produces the correct 1:45:00. This is exactly the same borrowing operation used in decimal subtraction ("12 minus 5, borrow from the tens column"), just triggered at 60 instead of 10, and it has to apply independently at both the seconds-from-minutes and minutes-from-hours boundaries.

Why totals are often shown two ways

A duration like "1 hour 30 minutes" and "1.5 hours" are the same amount of time, but they're useful in different contexts: the base-60 form is what a human reads off a clock, while the decimal form is what payroll, billing, and spreadsheet formulas actually compute with, since decimal hours multiply cleanly by an hourly rate. Converting between them is just multiplying or dividing by 60 (and 3600 for seconds) — trivial once you're clear on which base you're starting from, which is exactly the conversion atime calculator handles automatically so you don't have to do the base-60-to-base-10 conversion by hand.