“ethics aside” truly a starter for a qa
John
Doe, related to Derrick Nippl-e perhaps? (Fry and Laurie)
Apparently no-one did it yet, so I’ll name my child +++ATH0
Ask Robert’); DROP TABLE Students; 's mum how it went.
Ah, little Bobby Tables we call him
Anyone remember when Chrome had that issue with validating nested URL-encoded characters? Anyone for John%%80%80 Doe?
Frontend devs hates this guy.
Still better than Jennifer Null I guess
It’s time to log off and get a vasectomy
It’s impossible to represent that on paper. It could be misrepresented as a specific number of spaces. Depending on the position on the paper, it may also be hard to tell if the carriage return comes with the line feed. Unless you want the document to be in ASCII or EBCDIC, it’s like writing an ambiguous math problem where the answer is different depending on how you were taught about the order of operations. Don’t do this to your kid, Abcde.
I’m not american and I’m glad I’m not but intended if someone could enter a bunch of zero width spaces
C programmers would ask whether a null-terminated name would be acceptable
Little Bobby Tables
Once I was tasked with doing QA testing for an app which was planned to initially go live in the states of Georgia and Tenessee. One of the required fields was the user’s legal name. I therefore looked up the laws on baby names in those two states.
Georgia has simple rules where a child’s forename must be a sequence of the 26 regular Latin letters.
Tenessee seemed to only require that a child’s name was writable under stone writing system, which would imply any unicode code point is permissible.
At the time, I logged a bug that a hypothetical user born in Tenessee with a name consisting of a single emoji couldn’t enter their legal name. I reckon it would also be legal to call a Tenessee baby 'John '.
im sure the devs tasked at fixing that bug loved u ;-)
Sounds like you did a thorough job as a QA tester. As a software engineer, I love to see it.
By the time the app was due to go live, we’d only reported bugs with the signup and login flows. This was misinterpreted as there only being issues with the signup and login flows, and the app launched on time. In reality, it was impossible to get past the login screen.
And then let me guess… Of course the QA testers get the blame, when in reality it’s either management or marketing that wanted to pushe the app out.
Blaming us would be too close to root-cause analysis for them even to consider. We weren’t normally QA testers, but they’d left it until too late to hire internal QA, so roped in the developers (us) from a SaaS vendor their app replied on as emergency QA.
why settle for \n when you can go for the stylish carriage return
so
John\r Doe? depending on the software, when it gets printed, the carriage return will moves the cursor to the start of the line without moving a line down, becoming\x20Doe.This is the ideal rendition, I would say. On a related note, I just love it when there are backspaces in my filenames
¿Porqué no los dos? A nice \r\n, Windows style.
Gotta band it Windows tho, it just feels right, I want to enjoy my fake typewriter
No, cause “John\nDoe” messes up my regex. Sorry, out of the question.
no one is “good” with regex.
Then who’s coming up with all the bits that I copy/paste off the internet? The regex dragon?
they likely aren’t good regex’s ;P … anything with more than, say, 6 operators is probably missing an edge case or will be outdated in a year (and then it’s impossible to determine its original intention)
There was only one, we’re all still copying from him or her.
From what I’ve seen, it’s Cthulhu.
Be funny as fuck if Canada started extradition procedures when he landed
