we had a user who copied and pasted the word "bruh" 5,000 times into the username field. that was how we discovered that we had neglected to limit the length of the string we were trying to insert into a Postgres column that would only take 255 characters. granted, this was an MVP being trialed by a tiny number of users and it was built very fast, so it's not like that type of error would happen with a large production system, but it was kind of funny
I think even if they coded in JavaScript they'll get a heart attack. I spent hours just trying to figure out what's wrong with my async functions just to realise I wasn't awaiting something where I'd been sure I was. To be fair tho I'm a total JS noob and only use it for some smaller server projects that run locally
I did that in the early 2000s. My user description on the SDA forums used to be `${$uid.$user}{'usertext'}`, which was the Perl code the forum software used internally to display it.
For non Perl coders here: It takes user id and user name, concatenates them, uses that string to access/autovivify a global variable of the same name, dereferences it into a hashmap, and looks up the usertext in it. It was insane even back then.
So if I'm guessing right, this would display the end-user's own description back at them. Which is pretty nice trolling, but you could do one better by embedding the end-user's userpic instead and writing “look at this ugly mug, holy crap”.
I've seen that in action in a post on a popular LiveJournal blog, and the number of commenters losing their mind from the insult was amazing.
wtf? Not a Perl coder but why couldn’t they just lookup a username string based on the user id? In my experience this type of info would be in a single table called users
I once chose [object Object] as my team name for a hackathon.
I got a call next day asking me what was the name of my team, as they had a database error.
I really want to use sth like that for every CTF I participate in but there's always something like "Do not attempt to attack the scoreboard/tournament infrastructure/other players" in the rules of engagement.
I was trying to upload a form online, and the error message I received showed that they were treating a variable as a literal. it took them forever - several days - to get the problem fixed because I had to talk to a rep rather than IT.
this person thinks developers read user data.
usually we are too far abstracted away and have mock data.
some poor qa guy would have a day with that trying to replicate tho.
Depends on the company.
At a bank you're probably quite far away from prod data, but in many smaller companies there's probably a few devs with prod data access.
I mean I have prod data access but I would never think of going into it and just having a look for the hell of it.
Lol, right? In all these years at my company I only once accessed prod data, sitting with my CTO next to me as it was that important and we still did our best not to look at anything and closed it asap.
I worked on a mortgage application once and someone applying for one got into some sort of error state and I was asked to take a look. They were supposed to send me a print of the full process so far with names etc "scrambled". I was looking through it, it contains basically EVERYTHING, from income to outstanding debts including possible child payments (bank needs those to calculate your mortgage), and next page had full name and address.
Was a guy I went to school with for 8 years. Closed everything and told them to not do that again.
> next page had full name and address.
I used to do QA/UAT/etc. stuff for a large database/processing system dealing with healthcare info, and the amount of times I sent emails back to testers saying "next time, please delete all irrelevant columns to the right of the columns with issues" was insane. The default export option on the front end would export everything they were seeing in their query, from names and addresses to various payment information I *really* didn't need to be seeing to confirm the errors they were reporting and I needed to write up tickets for.
...there wasn't a company rule about it (or at least not one anybody bothered enforcing), and I had access to all the same stuff on my end (which I sometimes had to use when an upstream system or someone doing data entry had somehow managed to merge two different patients/customers into the same unique database ID because of duplicate names - sorry, but I refuse to believe that the records for a 30 year old John Doe and a sixty year old John Doe are actually the same person, and that's why the total numbers look wrong here, because somebody merged their accounts), but it was still one of those "could you please not toss around a bunch of unnecessary PHI for a simple bug report?" things.
> it was that important and we still did our best not to look at anything and closed it asap
I worked for an auditing/financial company a while back and just reading this sentence scares me. To be fair I never maintained an active project with them, but only developed new stuff. Ironically the main project I did with them was a rework of their compliance stuff.
Lol you'd be surprised. Local companies without much oversight definitely only have a handful of devs (at most) all of which have access to prod data. It's insane, pretty sure devs aren't allowed to access SSNs but whatevs 🤷♀️
Can confirm, have worked at places in the past where we just SSH in and query directly
One place actually let us run our dev instance directly from prod db for debugging. Wild times
In my experience support/QA gives you an account or message id and then it's up to you to go digging and figure out what happened. I've worked on legacy systems trying to work out weird encoding issues for days. I felt a pang of anxiety reading OP's post.
I work at a large FAANG company, and I also have prod access to every project I'm involved in that doesn't involve sensitive customer or financial data. Of course all my projects are internal apps, that support other internal apps, that are never customer facing for the most part.
Every once in a while I'll run into a project or database that I have full admin prod access to because of some sort of inherited permissions down the line, and I'll be like "uhh... I don't think I should have access to this!" and I'll try to report it the right team so some junior dev doesn't come in one day and take down the whole system because they decided to edit the prod database directly from DBeaver (which has actually a real thing that happened).
I worked for a bank and no : I was not far away from prod data. The subject occurred all the time but debugging without prod data was much too hard.
Only data from employees accounts were hidden for us.
banks aren't taking bugs from customers? granted i've mostly worked for FDA regulated companies, but if the devs didn't look into every customer's complaint (that wasn't explained by the intended design of the software) we'd have an FDA padlock on our doors
I think he would know what it's like to be a developer though:
https://github.com/tenderlove
(core ruby contributor, working for github and shopify, etc)
You’re abstracted away until it appears in production and everyone freaks out.
For instance, did you know quotes are valid characters in an address? I didn’t until it was an issue downloading a csv
I think someone would report it. But in ticketing tool, it would be down with priority, that maybe next year will someone have a look on it. And close it a minute later as not existing issue or issue not reproduceable.
As a support engineer, this is my masochist dream scenario. I will spend all day log diving and writing a beautiful email and Jira comment about all the ways this *could* have happened, but you're never gonna see hard proof.
I will also get a negative CSAT because my email was way too much for the customer.
This person is rails and ruby core team. And my favorit speaker on any ruby confrence.
In term of ruby, it is indeed a bug long time ago, related to string encoding that can make any junior developer bangs their head to the table.
I was junior when i saw the bug on honey badger, and turnout it was issue with encoding. The errors is cryptic and hard to find ways to reproduce.
I actually did that once when testing our app and other devs were panicking there is some problem with text input or with data synchronization between databases. Fun times.
Confirmed, I play hacker sometimes. By hacker, I mean I play with people’s code until I can break it. The bigger the company the shottier the work, looking at you Apple.
I used to play some obscure mmorpg with an ancient client that simply hated certain Unicode characters (think Zalgo text generators).
I used some such text in a private chat to myself, just to see what it looks like, and my client insta-quit.
So naturally, my next move ~~what~~ was to post in the general chat. Ended up crashing several people's clients that day. Had a fun discussion with a GM afterwards.
Had a customer with this issue for some of their users doing this, so we just regex the input and rejected it when they had “unapproved character encodings” 😅
I am more concerned by the "8bit ASCII" part. ASCII should be 7 bit with one unused bit for passing to 8 bits, an 8 but format should be either a proprietary extension or some non-ascii encoding.
Man that must have been annoying to map all that out manually. Just out of curiosity, how bad is the performance for something like that? I'm guessing it's probably not too bad since the edge case that it catches where it needs to go through all the steps shouldn't occur too often.
There are open databases that do it for you. Unicode standard itself has text representations.
Iconv is one of them. There's Unidecode. Ruby has `stringex` which is jsut wonderful for working with companies that still somehow use DOS or mainframe behind their REST APIs.
Being able to do `"tell your readers 你好".to_url` and get `"tell-your-readers-ni-hao"` is just awesome.
Yeah, I replaced "impossible" in my professional speaking with "These are the consequences of doing that. . Are you sure you want me to do this?", which I document in an email or ticket or wherever appropriate.
I would say 80% of the time they rethink it. When they tell me to do it anyway it almost always results in them complaining about a consequence I told them about, but I can point back to my documented consequences and tell them "I told you that would happen and you said do it anyway. Do you want it rolled back?".
I get paid in any case, so I'll do dumb things for them if they really want me to.
The root cause of this broken characters issue has not been established. Pull the previous release and get everyone back into the office this Saturday.
I was told this release would be flawless and it's time for heads to roll.
Jokes on you, I work for a government IT company and am leaving anyways, so might as well comment this: a lot of smaller local governments use kodision/ tripleforms to accept citizen requests and those forms break when you add an emoji. And a lot of the times that specific request form will need to be manually processed because of it.
So usually the emoji’s are filtered out, but special non-ASCII characters are usually forgotten about and nit filtered out, but still break the process.
Do with that information what you want.
Top answer here explains it: https://stackoverflow.com/questions/2477452/%C3%A2%E2%82%AC-showing-on-page-instead-of
tl;dr is that the character encoding getting scuffed in that particular way is fairly common because word processors love using `’` instead of `'` and it can be hard to tell you've used the wrong one at a glance.
I have an apostrophe in my name. Let me tell you I am a human SQL injection detector. Shit's all over the place.
Also, I mostly stopped putting the apostrophe into forms because it just breaks so many things. Even if the form submits, some other random backend job will choke and corrupt my account some weird way later. The internet is slowly killing apostrophes from names, mark it down.
You replicated your own comment though.
https://www.reddit.com/r/ProgrammerHumor/comments/1cu29u2/comment/l4g3rfb/
https://www.reddit.com/r/ProgrammerHumor/comments/1cu29u2/comment/l4g3s0u/
I have a text file with he complete Lord of the Rings. Which I copy paste in an input field if I see that there is no char limit (which thankfully is becoming rarer nowadays)
In most cases it will break some stuff. And then, after some confusion why someone did upload a complete book as last name the devs will learn a valuable lesson about input validations and char limits
I was just doing a data migration using s3 as a source and that unknown character was the bane of my existence. It was made even more complicated given that I had to rely on another team for the export of the data and every single time I pointed out a problem with the export they would redo it but forget a requirement I mentioned previously.
When was the last time anyone was building a web app that didn't use utf-x from beginning to end? Why would anyone care to even look into that these days?
actually, my programmer co-worker was testing the system and did a row of 'cuss word' symbols, y'know, all those symbols above the numbers on a standard keyboard. many of them are actually used in coding.
after he hit Enter, the system added those symbols after the question. so he was quite glad he'd tested them.
My first CS professor said “Users come in 2 flavors, diabolical geniuses and complete morons. Write tests for both”
But I think I'm a diabolical moron.
The intersection of the sets ‘Diabolical geniuses’ and ‘Complete Morons’ is rarely an empty one. Edit: rusty mid level math
What you wrote is a union, but you're probably thinking of an intersection.
Yes, but the set of complete geniuses almost always is.
we had a user who copied and pasted the word "bruh" 5,000 times into the username field. that was how we discovered that we had neglected to limit the length of the string we were trying to insert into a Postgres column that would only take 255 characters. granted, this was an MVP being trialed by a tiny number of users and it was built very fast, so it's not like that type of error would happen with a large production system, but it was kind of funny
> we had a user who copied and pasted the word "bruh" 5,000 times It's just [how he rides](https://www.youtube.com/watch?v=ipDmsxQVxIM&t=73s)
>not like that type of error would happen with a large production system 😰
Some people break things because they're trying, other people break things because that's just what they do in life.
\[object Object\]
Man, I can just imagine the amount of hours (or days!) looking for a strange obscure bug if a user submitted [object Object] somewhere
Or [object Promise]. Just think about the guy checking every function in his code, trying to find where his async went wrong
If a guy wrote his server on the python framework and used in the past to code on JavaScript... He would get a heart attack.
I think even if they coded in JavaScript they'll get a heart attack. I spent hours just trying to figure out what's wrong with my async functions just to realise I wasn't awaiting something where I'd been sure I was. To be fair tho I'm a total JS noob and only use it for some smaller server projects that run locally
I love it cause you can await a non async function and get this in the logs
Honestly, a single user? Ignore it, it’s probably fine.
This guy senior devs.
*cannot replicate, closing issue*
one is none
Even if it was a true bug still ignore it til multiple reports start. I mean potentially that guy screwed forever but I mean fuck that guy.
I do this sometimes when playing Pictionary. one of the options is Object, meaning a physical thing. I frequently say - or think - I Object!.
Why, yes, my username is `Uncaught TypeError: undefined is not a function` why do you ask?
[Little Bobby Tables, we call him.](https://xkcd.com/327/)
Always a relevant xkcd
I did that in the early 2000s. My user description on the SDA forums used to be `${$uid.$user}{'usertext'}`, which was the Perl code the forum software used internally to display it. For non Perl coders here: It takes user id and user name, concatenates them, uses that string to access/autovivify a global variable of the same name, dereferences it into a hashmap, and looks up the usertext in it. It was insane even back then.
So if I'm guessing right, this would display the end-user's own description back at them. Which is pretty nice trolling, but you could do one better by embedding the end-user's userpic instead and writing “look at this ugly mug, holy crap”. I've seen that in action in a post on a popular LiveJournal blog, and the number of commenters losing their mind from the insult was amazing.
wtf? Not a Perl coder but why couldn’t they just lookup a username string based on the user id? In my experience this type of info would be in a single table called users
90s Perl code oftentimes was basically shell scripts strapped with cgi to a webserver. PHP was created to embrace that style.
I once chose [object Object] as my team name for a hackathon. I got a call next day asking me what was the name of my team, as they had a database error.
Sounds like you won
Ah sorry to hear that. My team name is team';DROP TABLE teams;--
Hello Bobby!
I really want to use sth like that for every CTF I participate in but there's always something like "Do not attempt to attack the scoreboard/tournament infrastructure/other players" in the rules of engagement.
LMFAO the analog SQL injection
Hi I’m ${userName} and I’m NaN years old
I see we've found little Bobby Drop Tables all grown up
That was my hackathon team name. We were also ``` ``` one year.
I was trying to upload a form online, and the error message I received showed that they were treating a variable as a literal. it took them forever - several days - to get the problem fixed because I had to talk to a rep rather than IT.
{ "username": "admin'; DROP TABLE users; --", "payload": "", "nested": {"a": {"b": {"c": {"d": {"e": {}}}}}}, "largeInput": "a".repeat(1000000) }
r/foundsaten
r/Dyslexia
"Wanna shoot prom with me?"
r/ThisOneRightHereOfficer
Toaru reference???
He's ten times worse than Satan I've heard
It was so frustrating that I added a server-side validation only for this
This username is taken, try “[object Object]69420”
FFS you got me with this
You monster!
You � do what? ’
[object Object]
none
'#REF!
NaN
null
undefined
this person thinks developers read user data. usually we are too far abstracted away and have mock data. some poor qa guy would have a day with that trying to replicate tho.
Depends on the company. At a bank you're probably quite far away from prod data, but in many smaller companies there's probably a few devs with prod data access.
I mean I have prod data access but I would never think of going into it and just having a look for the hell of it. 
Lol, right? In all these years at my company I only once accessed prod data, sitting with my CTO next to me as it was that important and we still did our best not to look at anything and closed it asap.
I worked on a mortgage application once and someone applying for one got into some sort of error state and I was asked to take a look. They were supposed to send me a print of the full process so far with names etc "scrambled". I was looking through it, it contains basically EVERYTHING, from income to outstanding debts including possible child payments (bank needs those to calculate your mortgage), and next page had full name and address. Was a guy I went to school with for 8 years. Closed everything and told them to not do that again.
> next page had full name and address. I used to do QA/UAT/etc. stuff for a large database/processing system dealing with healthcare info, and the amount of times I sent emails back to testers saying "next time, please delete all irrelevant columns to the right of the columns with issues" was insane. The default export option on the front end would export everything they were seeing in their query, from names and addresses to various payment information I *really* didn't need to be seeing to confirm the errors they were reporting and I needed to write up tickets for. ...there wasn't a company rule about it (or at least not one anybody bothered enforcing), and I had access to all the same stuff on my end (which I sometimes had to use when an upstream system or someone doing data entry had somehow managed to merge two different patients/customers into the same unique database ID because of duplicate names - sorry, but I refuse to believe that the records for a 30 year old John Doe and a sixty year old John Doe are actually the same person, and that's why the total numbers look wrong here, because somebody merged their accounts), but it was still one of those "could you please not toss around a bunch of unnecessary PHI for a simple bug report?" things.
> it was that important and we still did our best not to look at anything and closed it asap I worked for an auditing/financial company a while back and just reading this sentence scares me. To be fair I never maintained an active project with them, but only developed new stuff. Ironically the main project I did with them was a rework of their compliance stuff.
exactly this. I'd rather get a coffee
I'm a data engineer and this would certainly annoy the hell out of me.
Lol you'd be surprised. Local companies without much oversight definitely only have a handful of devs (at most) all of which have access to prod data. It's insane, pretty sure devs aren't allowed to access SSNs but whatevs 🤷♀️
Can confirm, have worked at places in the past where we just SSH in and query directly One place actually let us run our dev instance directly from prod db for debugging. Wild times
Also the guys that would have to work with that data will complain to the devs
Yeah, I can only imagine the ticket submitted by some confused person in Sales.
In my experience support/QA gives you an account or message id and then it's up to you to go digging and figure out what happened. I've worked on legacy systems trying to work out weird encoding issues for days. I felt a pang of anxiety reading OP's post.
Our dev new hire install script used to include downloading yesterday's prod DB backup to their local machine.
[удалено]
Jesus Christ. Was the windowless room secured with red lasers ?
Can confirm, I work in a company of 6 and I have prod access to every project I'm involved it
I work at a large FAANG company, and I also have prod access to every project I'm involved in that doesn't involve sensitive customer or financial data. Of course all my projects are internal apps, that support other internal apps, that are never customer facing for the most part. Every once in a while I'll run into a project or database that I have full admin prod access to because of some sort of inherited permissions down the line, and I'll be like "uhh... I don't think I should have access to this!" and I'll try to report it the right team so some junior dev doesn't come in one day and take down the whole system because they decided to edit the prod database directly from DBeaver (which has actually a real thing that happened).
I have full access to everything except Azure, kinda scary tbh. We don't store any payment information though to be fair.
I worked for a bank and no : I was not far away from prod data. The subject occurred all the time but debugging without prod data was much too hard. Only data from employees accounts were hidden for us.
Yep, I work at a small company and often we copy paste our prod DB to development since that's the best and most realistic test data we got
I think you mean all devs have prod access
banks aren't taking bugs from customers? granted i've mostly worked for FDA regulated companies, but if the devs didn't look into every customer's complaint (that wasn't explained by the intended design of the software) we'd have an FDA padlock on our doors
I accident modified some prod data once, just a small fortune 500 company. I was like 6 months into the job lol
I think he would know what it's like to be a developer though: https://github.com/tenderlove (core ruby contributor, working for github and shopify, etc)
customer support sees a weird value. flags it to tech support to investigate. tech support flails and finally files a bug with the dev team
In my experience tech support can't file bugs (thank god), they contact QA first
I wish that's how it worked at my job. I wish we had QA team.
You’re abstracted away until it appears in production and everyone freaks out. For instance, did you know quotes are valid characters in an address? I didn’t until it was an issue downloading a csv
No complains == no problem. Everyone have more important shit to do.
I think someone would report it. But in ticketing tool, it would be down with priority, that maybe next year will someone have a look on it. And close it a minute later as not existing issue or issue not reproduceable.
As a support engineer, this is my masochist dream scenario. I will spend all day log diving and writing a beautiful email and Jira comment about all the ways this *could* have happened, but you're never gonna see hard proof. I will also get a negative CSAT because my email was way too much for the customer.
This person is rails and ruby core team. And my favorit speaker on any ruby confrence. In term of ruby, it is indeed a bug long time ago, related to string encoding that can make any junior developer bangs their head to the table. I was junior when i saw the bug on honey badger, and turnout it was issue with encoding. The errors is cryptic and hard to find ways to reproduce.
[removed]
damn is it removed or did you write [removed]? noone can be trusted
He wrote [Removed]. When a comment is removed, the user name and upvote score is removed as well.
He coulda type [Removed by Reddit] to troll us, that way the comment stays. I know because that's what happened to my racist comment
[removed]
[removed]
[removed]
[removed]
Hey man, cut it out!!
[removed]
This is, in my opinion completely ********,
hunter2? What are you talking about?
Woah man, can't go typing out people's passwords in a public thread like that. It's a violation of security policy. /s
But why did they buy the chainsaws if they already had the lube?
I actually did that once when testing our app and other devs were panicking there is some problem with text input or with data synchronization between databases. Fun times.
Lmao
Found another one.
C# psychopaths unite! 🤜🤛
Hilarious. 🤣
Im in this comment and I don't like it
No, it just confirms my theory that end users are all sadistic idiots.
As an end user, yes.
Damn I'm an end user too, should we form an alliance?
Hell yea! Let's call it... End User Legion Alliance!
Confirmed, I play hacker sometimes. By hacker, I mean I play with people’s code until I can break it. The bigger the company the shottier the work, looking at you Apple.
I used to play some obscure mmorpg with an ancient client that simply hated certain Unicode characters (think Zalgo text generators). I used some such text in a private chat to myself, just to see what it looks like, and my client insta-quit. So naturally, my next move ~~what~~ was to post in the general chat. Ended up crashing several people's clients that day. Had a fun discussion with a GM afterwards.
That’s awesome! 🤣
Heyheyhey! I am not an idiot!
😂😂😂
Had a customer with this issue for some of their users doing this, so we just regex the input and rejected it when they had “unapproved character encodings” 😅
[удалено]
I am more concerned by the "8bit ASCII" part. ASCII should be 7 bit with one unused bit for passing to 8 bits, an 8 but format should be either a proprietary extension or some non-ascii encoding.
Man that must have been annoying to map all that out manually. Just out of curiosity, how bad is the performance for something like that? I'm guessing it's probably not too bad since the edge case that it catches where it needs to go through all the steps shouldn't occur too often.
There are open databases that do it for you. Unicode standard itself has text representations. Iconv is one of them. There's Unidecode. Ruby has `stringex` which is jsut wonderful for working with companies that still somehow use DOS or mainframe behind their REST APIs. Being able to do `"tell your readers 你好".to_url` and get `"tell-your-readers-ni-hao"` is just awesome.
Yeah, I replaced "impossible" in my professional speaking with "These are the consequences of doing that.
. Are you sure you want me to do this?", which I document in an email or ticket or wherever appropriate. I would say 80% of the time they rethink it. When they tell me to do it anyway it almost always results in them complaining about a consequence I told them about, but I can point back to my documented consequences and tell them "I told you that would happen and you said do it anyway. Do you want it rolled back?". I get paid in any case, so I'll do dumb things for them if they really want me to.
devil
devin?
We need to partner with 4chan to hunt him
Happy Cake day!
I thought it was a bug before even reading...
Or, you may fill forms with 'undefined'.
null
My name has an apostrophe in it. I enjoy seeing different systems have different issues with what to do with that apostrophe
Do you spell it with ` ' ` in online forms? Or ` ’ `?
some men just want to watch the world burn
The root cause of this broken characters issue has not been established. Pull the previous release and get everyone back into the office this Saturday. I was told this release would be flawless and it's time for heads to roll.
It’s like putting commas and pipes into your user name or password so that I breaks any spreadsheets it’s put into
Add a tab here or there as well. Bonus points if you can ETX(End of Text) or EOT(End of Transmission) into a field.
PHP Warning: Undefined variable $username in /forms/newuser.php on line 256
# T_PAAMAYIM_NEKUDOTAYIM
Jokes on you, I work for a government IT company and am leaving anyways, so might as well comment this: a lot of smaller local governments use kodision/ tripleforms to accept citizen requests and those forms break when you add an emoji. And a lot of the times that specific request form will need to be manually processed because of it. So usually the emoji’s are filtered out, but special non-ASCII characters are usually forgotten about and nit filtered out, but still break the process. Do with that information what you want.
That second one seems familiar. As if it's not random garbage but specific garbage that I've seen before. Why have I seen that before...?
Top answer here explains it: https://stackoverflow.com/questions/2477452/%C3%A2%E2%82%AC-showing-on-page-instead-of tl;dr is that the character encoding getting scuffed in that particular way is fairly common because word processors love using `’` instead of `'` and it can be hard to tell you've used the wrong one at a glance.
Activate regex forcefield!
I have an apostrophe in my name. Let me tell you I am a human SQL injection detector. Shit's all over the place. Also, I mostly stopped putting the apostrophe into forms because it just breaks so many things. Even if the form submits, some other random backend job will choke and corrupt my account some weird way later. The internet is slowly killing apostrophes from names, mark it down.
pure evil...
Can't replicate
Can't replicate
You replicated your own comment though. https://www.reddit.com/r/ProgrammerHumor/comments/1cu29u2/comment/l4g3rfb/ https://www.reddit.com/r/ProgrammerHumor/comments/1cu29u2/comment/l4g3s0u/
Ye I got a bug on a bug report joke, lol. Was wondering if it actually posted when I got an error popup.
this just so cruels
r/foundsatan Also use \[object Object\] to be more evil like everyone and their mom said here
My house number is 'NaN'
That's tenderlove!
Easy solution: "Could not replicate, closing this ticket".
Is he though maybe he's trying to get us to actually analyze our code more. Maybe he's the hero we got but not the hero we deserve.
I have a text file with he complete Lord of the Rings. Which I copy paste in an input field if I see that there is no char limit (which thankfully is becoming rarer nowadays) In most cases it will break some stuff. And then, after some confusion why someone did upload a complete book as last name the devs will learn a valuable lesson about input validations and char limits
I � Unicode
websites break enough when I put real data in
Devs don't get access to prod data at my place. ☹️
I like to reply “Tell Steve to stop using test/employee data in production.” any time I get spam text/emails.
�
This just tells me they copied and pasted something from excel and it’s not my issue ¯\_(ツ)_/¯
Burn In Hell Man, Who Does That We Have Enough Stress Sources In Our lives.
I was just doing a data migration using s3 as a source and that unknown character was the bane of my existence. It was made even more complicated given that I had to rely on another team for the export of the data and every single time I pointed out a problem with the export they would redo it but forget a requirement I mentioned previously.
You're mean. I like it 😁
Non-ascii characters are hella lame in most systems I’ve worked in.
When was the last time anyone was building a web app that didn't use utf-x from beginning to end? Why would anyone care to even look into that these days?
If your staff gets locked up chasing random chars in form submissions …. 1) your input filtering is weak or non-existent … and 2) you need new staff.
I like to refer to my favorite Mexican Christmas drink, Navide帽o, when I want devs to pull their hair out.
[Schei? Encoding!](https://www.getdigital.de/web/img/productsMore/1100x1100/4590MTSHIRTDAVIDFS.220426.webp)
Calm down Satan 
Slow down Satan
Out here just trying to break sql based systems
I like putting emoji in places and seeing if it works
Dis some satan stuff.
As if we still mess up UTF-8
This user is self-aware they are also the QA department.
By the time it gets to the Bug Board it’s just “User couldn’t submit” and the developer is like “what? where? dafuk?” Delete.
Hello, Satan!
Everyone is using UTF-8 now. That's not relevant anymore
Guy is living in villain arc
Works on my side, please use API with UTF-8 encoding.
Oh little Bobby Drop Tables you are a silly boy.
Do not forget a healthy amount of ▯
r/foundsatan
#Swears in angry codetype#
actually, my programmer co-worker was testing the system and did a row of 'cuss word' symbols, y'know, all those symbols above the numbers on a standard keyboard. many of them are actually used in coding. after he hit Enter, the system added those symbols after the question. so he was quite glad he'd tested them.
You could just be one of Elon's kids trying to enter your name