I'm working with some data that has a large number of date formats within a single document - day seconds, week seconds, ISO8601, ticks, some with hardcoded offsets and others with different datums ... it would be quite funny I think to throw in a new column in the Hebrew calendar, just to join the party, so to speak.
The Hebrew calendar is a marvel of historical engineering and complexity. Both solar and lunar with exceptions to accommodate Shabbat and other holidays, and be consistent with the Torah.
That is a very good link. The top comment has direct implications for any software / report generation dealing with tidal (-> lunar) cycles. Perhaps using something non-ISO to store time on the inside could have its benefits.
This was pretty fun! Sometimes the stories were a bit harder to parse than others, but honestly, that's pretty reflective of what it's like being a technical person communicating with non-technical people.
Well, the puzzles are the same, only the clues and dataset are different. But you might want to do them again anyway, to polish up your scripts--on the last day of Hannukah, we'll be posting a more challenging dataset for you to try to speedrun.
And keep on the lookout for more data puzzles from us in the near future!
The phone number input requires dashes, which are entirely optional in general for communicating telephone numbers (dashes and parens only serve as decoration for readability these days).