• 4 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle
  • To be clear, please continue to enjoy your food the way you want it. Just know what the words that exit your mouth mean. Life shouldn’t be safe, and many of life’s greatest pleasures are not safe.

    Is it a Canadian beef problem? Nah, it’s just a problem with the definition of “safe food”. If the food is not cooked to 165F, then any bacteria, fungi, and parasites that are present could still be alive. There are no guarantees that the beef didn’t have tapeworms, and since ground beef is usually from multiple cuts, there’s a larger chance that a tapeworm has been ground up and spread throughout. It’s a tiny chance, but it’s still a chance. Steaks are less of a risk, because it’s a single cut, and the chef can visually inspect it.

    The waiver is stupid, but it has less to do with capitalism and more to do with the legal system. People sue for anything and everything, and I don’t blame companies for trying to defend themselves from that. They asked the dude to sign a waiver, because they’re afraid he doesn’t understand the risks and might sue if he gets sick.

    Funny thing is: in this case the guy didn’t understand the risks. He thought they were saying their beef is sketchy. What they were really saying is: all ground beef not cooked to 165F could be sketchy. I think he’s dumb, because he doesn’t know that a medium cooked burger involves risk but has been requesting it everywhere he goes. If he had known what a medium burger is, he would’ve just said “yeah yeah yeah”, signed, and ate the burger like an adult.

    I’m not you pal, buddy. (but we might be friends now)



  • Dude is incredibly stupid, because he’s been ordering under-cooked burgers without any conception of what he’s requesting for “Bob”-know-how-long.

    He might like medium-cooked burgers, but he has no idea what that even means. The food at the hotel isn’t less-safe than other places. They just didn’t assume he read the fine-print at the bottom of the menu and were the first to inform him that it’s not safe.

    Yeah, they delivered the waiver at the wrong time, but dude should’ve already known what he was ordering wasn’t safe. I order over-easy, soft-boiled, and sometimes sunny-side-up eggs. I know the risks, and I accept them.

    Unless you put an a ton of effort into it, ground beef is only safe well-done. To get safe under-cooked ground beef, you need to discuss your intentions with your butcher and grind the beef yourself. Even with grinding a single, quality cut of beef, you’re still gambling.

    Also, fuck you, I’m not your friend guy, here’s a rocket ship ().():::::::::::::::::D~~~~~~~














  • Yeah, this feels like “premature optimization”. When you design your applications and databases, it should reflect your understanding of the problem and how you solved it as best as possible. Using DATETIMEOFFSET NULL when you actually mean BIT NOT NULL isn’t saying what you mean. If you already understand that you have a boolean option and you think you might need a timestamp to track it, use 2 columns. Or an audit table. So sayeth the holy SRP.