It’s not like there are people checking for immortals, I think it would be flagged by a dmv employee or something when they dont believe a clear 21 year old is actually 150. Let’s assume it’s current day im caught and not bring speculation on what the US is like in the year 2139 is like.
You can use this to your advantage, by claiming it’s some sort of annoying mixup and it happened before. You can use this to sneak new info into the system when they need your help correcting the obvious mistake that you’re not 100 and get your dates reset.
…
So awhile ago I worked on a system that moved education records between 2 different systems at a university. It kept choking on one particular record; turns out the date of birth was in 1499, and MSSQL won’t store dates from before the start of the Gregorian calendar unless you specifically configure it to do so.
We sent a request through to have the record corrected - clearly someone has just typoed 1949 - and moved on, but maybe…
Just one question: on which keyboard are 4 and 9 close to each other to get typoed *X-Files music starts*
in the number industry we call it a transposition error and you can tell if the difference between the two is a multiple of 9.
All I can think of is a gruff, blue collar worker coming home, covered in oil stains. He hangs up his hardhat and lunch pail at the door. “You would not believe the day I had!” He says, “Some jackass put the 9 dies in the 6 press, and I had to spend all morning trying to pry open the hydraulics without fucking them up. After all that, I get a call that the serifs are too long on the ones and they’re getting sorted as sevens!”
It’s not about close position in this case, it’s that the idiot was typing quickly and hit the numbers in the wrong order. Also, a numpad was more likely used than the number row.
Or left hand hovering 1 and 4, right hand hovering in over 6 through 0.
Transposition error