Don’t forget to order null beers, and " DROP TABLE * BEERS
I’ve played enough games to know that he definitely forgot to check for integer overflow errors.
that’s the big number
A developer walks into a bar and orders one Budweiser’); DROP TABLE bartenders;
A table falls over and drops on the foot of the developer
An SEO specialist walks into a bar, saloon, watering hole, place to get drinks, neighborhood bar, dive bar, best mixed drinks, beer on tap…
Thank god, finally a bar that sells lizards and kills people who spend to much time in the bathroom, this place is perfect.
I’m reading this while sitting on the toilet. Do I have anything to worr… Oh fuck! I’m on fire! Help!
Damn. Need to wrap that whole bar in a try: except: that just silently fails. Solves all the issues and you go to another bar.
Exception:
Spits out entire codebase
In my experience silently failing just leaves you standing there waiting for your beer forever, or until someone reboots the universe.
“But if it silently fails then we won’t know there’s a problem until a customer reports it and we go looking for it!”
Yes, and that could be weeks before it becomes my problem again!
And weeks later, after that change has been rolled out to all the bars, the engineer now has to travel to every single one of them to fix it.
Customer: Can i use the bathroom?
Bartender: Ehhhh our bathroom is not available at the moment.
Customer: What?
Bartender: Not. Available…
def bathroom(customer): return False
Isn’t it weird that their job title is QA Engineer when their goal is to break stuff?
Who else is going to engineer the tools to break stuff?
QA Terrorist?
Did they order Bobby Tables beers though
Bobby ordered beers for the table, stack overflow caused them to black out
lesson: santize your bartenders inputs but also use hierarchical rbac to provide guests access to querying for amenities.
