TwoPhonesOneKid

I'm just pointing out you can get the same food with a quarter (at most) of the prep time and twice the flipping if you approach it experimentally at the same heat. Very much including basting. If you think steakhouses let steaks sit out before cooking them you're nuts—they might get nuked for five seconds for approximately the same effect. Letting them sit is just a convenience while prepping the rest of dinner.

Also, tenderizing the meat is about 10x as effective as letting it rest at room temperature. Not only does it warm the meat much faster, it reduces cook time, draws moisture out, and improves the crust. A minute of beating the shit out of the steak can trivially improve on an hour of sitting out (as if we have the time most days!). The grid-slice pattern is also very effective, even if it looks trashy. It's trashy because it's cheap and it works so well any cheap steakhouse will do it to obscure the shitty produce. Just make sure to do the tenderizing before you apply the salt.

Of course if you enjoy cooking, don't let my advice ruin it. Food is a lot more enjoyable if you feel satisfied eating it. Not everyone needs to optimize for cook-time.

I see this understanding that sql databases should do xyz by default as corporate dogmatism, kind of. A database is only as useful as it's used! I realize you haven't argued for this, but if we're collectively claiming postgres can handle 100% of the persistent database needs of an arbitrary app (a very common claim these days), we also need to accept that people will "abuse" sql databases to prioritize accessibility over coherency, which was always a major draw of NoSQL engines. I suspect most consumer apps can scale with some form of inconsistency just fine, even if this creates a PR rats-nest, but consumers are far more forgiving of incompetency than greediness. This is a very much an "understand your market" sort of decision to make.

So I see what you're saying, but I'd also like more async bindings that lean into customizing the behavior at query- or execution-time. You can build them today but you have to work around whatever sql-binding framework you use and it will still likely result in leaky abstractions.

Too late to edit, but probability and statistics do emphatically rely on past-certainty. The entire concept of using the past to predict the future, however, is just a convenience with no reasonable basis. Please appropriately hedge your comments as to not imply otherwise or be appropriately mocked in response.

This is precisely why I don't trust people who aver without receipts to show. Open the schools, goddammit!

Until I see some reasonable evidence that smaller process size cannot exist, i just see lazy people getting angry that someone disagrees with them. All of this "burden of proof" bullshit, aping like you're in some kind of formal debate rather than a conversation with a stranger, just screams "emotional asshole who can't deal with someone disagreeing with them and never learned how to engage in basic conflict resolution when they had the ability to engage in good faith and chose not to".

Y'all deserve all the mockery society can afford. I'm at least honest in that I see conflict is what we need more than ever if only to put people like you in your place.

Gawker was a far more valuable institution than both of the above. I'm not sure how you could claim otherwise: both papers just regurgitate ap headlines with misanthropic assholes managing the editing. Gawker at least managed to break news and contribute to discourse beyond the ivy-league toadies that contribute nothing substantial beyond dogmatic reverwnce for broken institutions that were wildly out of date a hundred years ago.

Centrist idiots blathering about institutional integrity and decorum destroyed this country. I refuse to let them gain power again. I far prefer gossip rags to imperial stooges: at least they're honest about their dishonesty. They also never stooped to the level of the new york times endorsing an obviously illegal invasion.

Granted, both are equally willing to cater towards the american demand for blood rather than justice. But at least I can blame the poeple actually at the capitol for january sixth. Who the hell can I blame for the mass-complacency and dogmatism of college-educated liberals aside from the very same ignorant mass? Until a better scapegoat arrives, the editorial boards of ivy-league-catering newspapers will have to do.

Why do people not read manufacturing consent? It's the only text american adults should be reading. Everything else doesn't matter.

This theory has held up poorly to other theories, such as the federal legalization of abortion. Positing a single cause, even a single dominating cause, is an incredibly, incredibly hard claim to demonstrate. I do believe that unleading gasoline had widespread social impacts, but this narrative is just lazy reduction with no benefit.

Personally, I think the easiest theory is simply economic prosperity. Most American problems these days can be described in terms of relationship to wealth. changes in education take decades to reflect in aggregate effectiveness. If nothing changes, I think we'll be facing a similarly-violent time period for likely the rest of our lives, even if we aren't there yet.

Meats don't really seal unless you're literally tarring them with char, and besides, juices leak from the side just fine. You really want to steam off the water content of a steak to get a better texture and fewer grease-runs. The entire meme about searing is literally just a decently crunchy texture. Flip steaks as much as you want.

The high "sear" temperature mostly implies a faster (and easy-to-follow) cook-time, but it still requires salting the steak to drain as much moisture as possible. It's certainly the smarter texhniwue, but not because it seals juices in.

(Also, "searing" a steak does in fact slow the rate of water loss, so it is easier to control cook-quality and easier to cook whilst distracted. But this undermines my main point that water content actually ruins the steak, and that you can get the same texture and taste with a different technique.)

Steaks being cooked naturally drain juice. The entire concept of searing a steak "sealing" the juices in implies a cooking paradigm that simply doesn't hold up to experimentation. You want to cook off water mass from a good steak—it's better flavor, better texture, and you're left with far less grease in your soup-catcher.

If you cook enough steaks, it's quite hard to get a dry one, and you can get excellent texture and taste despite draining the "juice" (which is like 80% of why you salt the steak to begin with—moisture = less even and harder to control cooking which results in a chewier crust).

Gawker still acted more mature in terms of the defamatory content than any given social network. This is as clear a case of revenge-murder as you can find. I just want to know who convinced Hulk Hogan anyone cares about him who doesn't already love him. As far as I know he's still the mustache guy of unknown import who was in that funny nanny movie in the nineties I saw at age four. who cares if he swings?

This was obviously about a man's insecurity leveraging the courts to destroy a publicly-valuable business beyond any reasonable conception of justice. Somehow the new york times was never held to the same standard when they published blatant lies and enabled the invasion of iraq and a million murdered.

Yea it turns out when you divorce politics from anything that matters it just becomes reality tv. Americans are too moronic to wield the power they claim today so it's hard to feel anything negative about this.

Hulk Hogan also destroyed gawker because he was too cowardish to admit he's a sex freak. Obviously Peter Thiel was involved because he's too cowardish to admit he's gay, but the takeaway is that our society is run by toddlers who never learned to regulate their emotions (let alone manage the wealth a capitalist society allegedly demands. Eg people outside of Buffet demanding to be taxed more and Chuck Feeney making the gates foundation look like money-grubbing assholes).

You could also cross in a raft. Or on a log. You can swim across (riskily, quite riskily) at the straight of gibraltar itself. We've known humans have been seafaring tens of thousands of years before our earliest archaeological evidence (although dugout canoes are likely just as old, it's very bad conditions for preservation outside of stuff like northern european bogs/the dead sea, and they often just look like logs underwater, not boats)—at no point has Australia been fully connected to continental asia. Hell, this is true for H Erectus, let alone h s sapiens—it's not difficult to believe H Erectus might have pieced together how to lash logs together.

On articles like this, I strongly recommend just ignoring the title. It's enough to make anyone with a mild background in the subject frustrated. The research itself remains incredibly interesting.

Typically the SQL engine will allow flexibility on this. Not all transactions need to prioritize write-to-disk confirmation over throughput. If you're collecting observability metrics, for instance, these don't have the same data coherency constraints your app model (account etc) demand. In this case you can accept the logical commit and the tiny chance it might not actually hit the disk. Postgres at least allows customizing this per transaction, I believe, although I'm not quite sure how it works if you compose transactions with distinct syncrhonization constraints.

Probablility and statistics are models that produce something we call certainty. This has no relation to actual certainty, aka knowledge. If you're making an abductive claim, you should state it as an abductive claim. Otherwise you're simply claiming true knowledge that is literally impossible to have.

Hume is deeply disappointed in you.