Has anyone dug into this enough to work out what exactly is the difference in measuring fertility rate vs gender compared to just measuring population percentage per gender? It’s got to be a very subtle difference, if anything.

Sometimes if you don’t use enough water or don’t stir it at the right time, pasta can stick to itself in the pan and the bits in the middle aren’t able to rehydrate/cook properly.

The schedule times above are off by an hour in some cases - this from the official app:

• SQ Fri 07:30 UTC
• S Sat 03:00 UTC
• Q Sat 07:00 UTC
• R Sun 07:00 UTC

UTC isn’t adjusted for daylight savings, so maybe that’s the source of the error?

It’s also not daylight savings in Europe (CET/BST) until 29th March and China doesn’t do daylight savings…

I feel like over-salting the tenderloin would spoil the flavour. And you don’t want to slow cook it, it will dry out.

But as a possible Irish twist: Replace the mushroom duxelle with white or black pudding? Should such a thing be available where you are

After being very confused by this picture, I just went down a rabbit hole researching the use of “corned beef” across the English speaking world…

As far as I can tell:

• US/Canada call this corned beef, and it’s made from brisket.
• UK/ex-Commonwealth call this salt beef, again made from brisket, and corned beef is very different mushy canned meat product
• In Ireland it seems, from looking at the website for one of their supermarkets, they just call everything corned beef? The canned mush, raw brisket, this - all “corned beef”?

I think I’ve figured it out somewhat.

Handling instance invite codes is definitely missing from the official stoatchat-for-web repo I built my frontend from - see: https://github.com/stoatchat/for-web/issues/639

But I think what confuses things when you ask around for help is that AFAIK a lot of people are using various forks and pre-made docker images that patch things like this.

I’m not sure these overlapping dots necessary represent the data so well… e.g. it gives the impression that London has only had about three terrorism incidents…

https://en.wikipedia.org/wiki/List_of_terrorist_incidents_in_London

Nice - thanks for this

Not my experience. I’ve had my X1C for a year now and have not had to ‘dial in’ a single thing.

Most of my prints are functional items in PETG of various colous. Some PLA for cosmetic parts. And I did some things in TPU earlier in the year. Probably been through like 10kg of filament on it.

Can’t think of a single serios print failure that wasn’t human error - e.g. forgot to clean the bed, didn’t support it properly.

My one gripe is that when changing PETG reels, it doesn’t always manage to wipe the nozzle very well leaving a few rogue stringy bits that usually just pull off.

And obviously I don’t love the closed-wall software situation, but their software is pretty good.

I also wasn’t aware so had a search.

If you don’t mind Reddit, this thread is interesting… https://www.reddit.com/r/rails/comments/133lcyl/can_someone_explain_what_happened_with_the/

Or there’s this… https://www.theverge.com/2021/5/3/22418208/basecamp-all-hands-meeting-employee-resignations-buyouts-implosion

Edit: Actually this is probably the most comprehensive summary: https://schneems.com/2021/05/12/the-room-where-it-happens-how-rails-gets-made/#the-basecamp-incident

Second paragraph is wrong - UK law mandates 20 paid days off, plus there are 8 paid public holiday days

Based on how you’re observing the loading move from 100% CPU ro 100% GPU, I would suggest that it is “working” to some extent.

I don’t have any experience with that GPU, but here’s few things to keep in mind with this:

1. When you use a GPU for video encoding, it’s not the case that it’s ‘accelerating’ what you were doing without it. What you’re doing is switching from running a software implementation of an HEVC encoder on your CPU to running a hardware implementation of an HEVC encoder on your GPU. Hardware and Software encoders are very different to one another and they won’t combine forces; it’s one or the other.

2. Video encoders have literally hundreds of configuration options. How you configure the encoder will have a massive impact on the encoding time. To get results that I’m happy with for archiving usually means encoding at slower than real-time for me on a 5800X CPU; if you’re getting over 100fps on your CPU I would guess that you have it setup on some very fast settings - I wouldn’t recommend this for anything other than real-time transcoding. Conversely, it’s possible you have slower settings configured for your GPU.

3. Video encoding is very difficult to do “well” in hardware. Generally speaking software is better suited to the sort of algorithms that are needed. GPUs can be beneficial in speeding up an encode, but the result won’t be as good in terms of quality vs file size - for the same quality a GPU encode will be bigger, or for the same file size a GPU encode will be lower quality.

I guess this is a roundabout way of suggesting that if you’re happy with the quality of your 100fps CPU encodes, stick with it!

3x 3 day pre-season tests for the new regs

Of course, but his cars have won around 40% of all WDC over the past 30ish years, and his record around major new aero regulations is exceptional:

• 1998: Two back-to-back WDC from first season
• 2009: Four back-to-back WDC from second season
• 2022: Two (soon to be three) back-to-back WDC from first season

If Newey ends up at Ferrari in time to design their 2026 car, Hamilton has either lucked into a second stunning career move or he’s known all along…