It's not my real birthday, it's just the one I use on the net. Like waterlesscloud I hop it will break something somewhere. Or at least amuse a fellow engineer.
Somebody else however suggested using 31st december 1969. Now that's just evil...
If you convert this to Unix epoch time (Seconds since 1970-01-01 00:00:00), the result will be -1.
Which is problematic in several scenarios:
- Databases which store dates in integer fields and maybe don't handle negative values.
- Other overflows unhandled by date parsers
- Libraries, which use -1 as 'invalid'.
