We'll get a sewing machine named SeamDeck.

I actually like this one lol.

In my little social circle DS4F generally substitutes for GLM 5.2 except it's the next best thing to free.

I know people who can cook a lot of food pretty well, but don't understand why they can't use a laser thermometer to check their meat.

Knowing really is half the battle.

If you cook enough you can tell by feel

The resistance of the steak is going to depend on what cut of meat you are poking (sirloin is stiffer than filet), the grade of meat (prime is more tender than select), how thick it is (thick cuts will yield more than thin), the age of the steer (young is more tender), the breed of steer (cooked Wagyu is more tender than Holstein), the age of the meat (wet aged is more tender than fresh killed), and what the steer was fed (corn fed is usually more tender than grass fed), among other things. [1]

It's not entirely a myth; if you've poked hundreds of steaks by the same supplier, same cuts, same grade, you'll eventually get a feel for them.

The thermometer analogy does carry over though. Some people are not there to be productive or good at their jobs. The job is about them, not their work.

And you can go your whole life without ever cooking or tasting a good steak. The people who can tell the difference will go elsewhere, and those who can't will come back.

And then there's always the boss who wishes he started a franchise but will go with what he has - he'll hire a bunch of newbies or foreign workers who know how to use a thermometer.

[1] https://amazingribs.com/ratings-reviews/best-thermometers/ho...

Yes, I meant given a similar cut ofc

Not with steak. That has been thoroughly debunked over and over. Just use a meat thermometer, it makes it easy peasy.

If you cook enough you won't even need to.

What I've really gotten out of this is that I'd like to learn how to use a (proper) meat thermometer when I make steaks.

Since this is HN, here's the maximum technology option: https://combustion.inc/

They have a thermometer with multiple sensors in it that finds the core temperature of the food you're cooking automatically, and predicts the rise in temperature over time. So the alarm goes off when it's time to pull and rest, which is absolutely amazing.

I have one of the Combustion thermometers, and I like it. I used it more than I expected. In particular, I use it for roasting chicken and for sous vide things more than anything else. Then I got a Breville Control Freak, and I used it much less. :)

For maximum techyness, Combustion, Inc. correctly identified that sous vide is normally an overdamped system. If you follow their instructions you can increase the water temp some and then bring it back down in order to move the system closer to critically damped and speed up your sous vide.

I've had a Combustion thermometer since they came out. The best uses for me are butterflied whole chicken on the grill and roasts in the oven. You can get extremely precise results and account for carry over cooking very easily. Huge leap in results.

Is this company owned by either Chris Young or Kenji Lopez-Alt? A few times I have seen them using this product and promoting it. I am curious if a bunch of influencer chefs decided to create a company to create this product.

AIUI it's owned by Chris, and Kenji is a fan, but doesn't have any ties other than that.

The funny part is steak is one of the easiest foods to cook without a thermometer

You don’t have to worry about undercooking like you do with most other meats and most steak cuts will be delicious anywhere from 11-130 (if you cook a filet to 130, it won’t be the best but it’ll still be good) and some can go even higher

It’s not like poultry where the range where it’s “good” is very small. A 170 chicken breast is almost inedible and 160 is not safe…

I agree with your broader point but the chicken food safety thing is missing a ton of important nuance. The safety comes from how long you hold the meat at the temp. 165 is the safe point if you are only holding for 10s. 145 is safe if you hold it for 10 minutes.

This is why sous vide is such a popular way to cook chicken. You can hold a breast at 145 for hours trivially.

Or understand risk ratios and don't rely on food that's 100% safe.

Sure. But then you need a thermometer.

You can be safe down to 135F if you give it enough time. https://douglasbaldwin.com/sous-vide.html#Poultry_and_Eggs

In particular, I use 135F for 90 minutes (75 minimum recommended) to pasteurize eggs that I am going to be putting into something that asks for "raw" eggs (egg nog, mayonnaise, etc.) that I will serve to other people (if it's just for myself, I'll probably just be lazy and use the raw egg). So far, nobody has noticed any difference from "raw".

160 degrees for a chicken breast is perfectly safe. Considerably lower temperatures can also produce microbiologically safe chicken when combined with sufficient holding time.

165 is a rough rule of thumb, not some magic number like the boiling point of water at 1 bar or something.

They have digital thermometers now that will map out the temperature curve and even predicted when the meat will reach core temp. You really don't need to use them many times before you internalize the behavior.

laser thermometer only measures surface temperature, unlike meat probes that measure internal temp. depending on the cut size or shape, initial temperature and probably some other factors internal temp will vary wildly for the given surface temperature. combustion probes mentioned in the sibling measure temp in several points at once to estimate readings even more precisely.

Ok, using a laser thermometer for food is hilarious. Thanks for this xD

It's not wrong for all food, surface temperature measurement has its place, you just have to understand it is surface measurement.

It is reasonable for measuring cooking environment. Like say pizza oven. Just have to be aware of things like right emissivity.

I use it to spot check the temp of my cast iron pan all the time.

for a caramel or some sauces it's legit

I've owned four OnePlus phones, but I've been buying other brands lately.

1. OnePlus became nearly as expensive as flagships but wasn't as good 2. The official software used to be almost-stock Android but they bloated it up 3. The ROM scene came to steadily lag several generations behind phone releases 4. Android/OnePlus ROMs are a worse experience than they used to be (dealing with proprietary camera drivers, SafetyNet) 5. They didn't keep pace when other brands committed to longer OS updates

They used to be a good bargain, a clean OS, and a good modding target if you wanted a ROM anyway.

The first two haven't been true for a while now, and the third became a lot less appealing on OnePlus.

I'm disappointed to see OnePlus go but the brand I loved has been gone for years.

Which other brands have you switched to?

Why would farmers disagree?

Based on the results of US elections in the past 30 years, farmers (as represented by rural voters in general) do not vote for candidates who support "collective benefit."

Sure they do they create co-operatives and pool resources together. They created banks, insurance that serve their needs. Farmers aren't some lone wolf. Farmers created universal health care in other countries like Canada.

They don't support the left and social politics of pushing trans, gay, racial, feminist policies. They believe in God and Christian values.

They work hard and expect others to and don't support a welfare state but that's different from collective benefits.

Yes, they've been told to fear "gay policies", whatever that actually means. Judging by the results, it's fair to say they are by and large uneducated -- except in their very narrow domain.

Fortunately we're seeing more JS DB libraries offering to read large numbers as the BigInt type.

Hm? JavaScript BigInts are arbitrary precision, and you need to use methods like BigInt.asIntN(64, a) to convert them to 64 bits

I hate this so much because you can’t nicely serialise a BigInt as JSON. Using a string is nicer but it only makes sense where int64 is used as an ID, not where it’s used as a number; and you don’t wanna have to configure this per field per query.

You can serialize a BigInt by specifying a replacer:

    const obj = { a: 9007199254740993n }
    JSON.stringify(obj, (_key, value) => typeof value === 'bigint' ? JSON.rawJSON(value.toString()) : value)

And then you end up with strings on the other side, not numbers.

No you don't? The example I gave produces

    {"a":9007199254740993}

not

    {"a":"9007199254740993"}

Oh, that's much worse! The JSON string `{"a":9007199254740993}` decodes to the object `{"a":9007199254740992}` with typical JSON parsers like JavaScript's `JSON.parse`.

If you're applying a replacer, then you'd supply a reviver when parsing:

    const json = '{ "a": 9007199254740993 }'
    JSON.parse(json, (_key, value, context) => /^\d+$/.test(context.source) ? BigInt(context.source) : value)

Yeah but now you have the world's biggest foot gun in your API.

IMO, I'm tending toward thinking that having types on your readable serialization format is a mistake, and that they should be always input to the (de)serializer instead.

JSON has arbitrary length numbers in the spec only.

This is simply not true? Or maybe I misunderstand what you mean?

I once lucked into a private tour of a Monet gallery. I asked the curator, "these paintings just don't look great, why should I be impressed?"

The curator responded that Monet, and impressionism in general, were a reaction to the then-new invention of paint sold in tubes. Previously a painter had to mix pigment powder right when they painted. So they usually couldn't paint outdoors where the wind would blow the powder, and they couldn't capture rapidly-evolving scenes.

Tube paint changed that. Impressionists started painting things in motion, or in shifting lighting like dawn. Their paintings were designed not to look good close up, but to be viewed at a distance, where the "pixelation" (so to speak) resolved into a coherent picture. They skipped on fine detail to capture something as fast as they could, because they could never do that before.

I still don't care for impressionism on an aesthetic level, but I learned something that day about art history and why some people appreciate art that I don't.

Lots of techical innivations enabled impressionism, but I would argue that synthetic ultramarine is the biggest one.

One should visit the Orsay museum to understand it, its curators know their job: impressionist paintings seem to glow from inside in the dim gallery.

Screens are bad at showing these colors, one still needs personal experience to get it.

My mom works at a credit union and the staff are constantly saving people from scams just because the customer came in and the staff had a chance to notice something fishy happening.

That'd leave even more room for drama. I'm imagining Gavin hiring thousands of cheap, unskilled laborers ("Hooli's industry-leading AI research team") to mash keys until they rediscover the prompt that generated middle-out compression with a patent-free clean room process. He never reproduces it because Gilfoyle's self-hosted LLM improved its own memory efficiency when when Dinesh got upset and started unplugging GPUs.

I remember an ORM that uses fake column types like `boolean` and `datetime` because SQLite doesn't enforce anything. That way the ORM knows how to deserialize the data. Strict mode prohibits this by only accepting column types SQLite recognizes.

My preference would be for SQLite to actually support commonplace data types. But as long as it doesn't, I can see the appeal in using the schema to specify what data you're storing in your database.