Just a few moments ago, my mind started wandering onto the subject of the most efficient way to store a calendar date in terms of number of bytes used.

[jaybird110127@dragonscave.space]

Just a few moments ago, my mind started wandering onto the subject of the most efficient way to store a calendar date in terms of number of bytes used. And as sometimes happens during such random wanderings, I hit upon a scheme for storing a month, date, and year within an arbitrarily-defined 100-year period in two bytes. The month (1 through 12) takes four bits, the date (1 through 31) takes five bits, and the remaining seven bits are used for the year (0 through 99). Additionally, this scheme allows for calendar modification or possibly some alternate calendars, to a certain extent. There can actually be up to sixteen months (0 through 15), any of which can have up to thirty-two days (0 through 31), and the year can actually go from 0 up to 127. Is this useful? Probably not. So be it.