well, truth be told, it's also for just coding practice (err, challenge~project), for me, too
it's a good next step for me in trying to get better at coding, via trying to tackle real world 'time and date' coding, as indeed there is some complex (for me) coding issues with it to solve.
----------
besides... we Americans, like our Norse math (base 12), and hate modern world's metric (base 10), and quite frankly, actually base 12 *IS* extremely practical:
3 and 4 (factors of 12), is much more useful than 2 and 5 (factors of 10), hehe
astronomy+time: basically anything with a curve or angle, as angles~degrees around a circle is 360, which 12 is a factor of, and probably a ton more practical uses too. Metric isn't as useful~great as it seems when you actually explore into the more important uses of physical (geometry+) mathematics.
Besides, what's the big deal with doing a conversion anyways, just look up what the conversion is (if you can't remember them), easy (you're not making the equation any harder by having to convert units).
--------
@Jay:
thanks Jay, I think I mostly get it now, just not quite able to grasp how the 'boolean_return (year % n = 0) -> if (IsDisible (year, n))' corresponds to checking in-whether it is an integer or double resultant value.
nevermind... I just finally comprehended how it works, lol... my brain though isn't quite at this level of thinking... as I finally just got it... lol:
if (remainder = 0), then (IsDivisble = true)
took me a long time to just now figuring this out, lol. (still a bit outside of my brain's intelligence level, as I got to think really hard to understand it, lol)