Also worth mentioning that universities generally see themselves as research facilities first and foremost. They teach students, because they want to get the next generation of researchers.

Sure, they’ll also do job training to some degree, because it’s a good argument to get more funding, but yeah, just not their primary goal.

I feel like direct marketing will become a lot more important.

AI-generated books flooding Amazon is already a thing. And even if AI at some point becomes capable of writing good books, I don’t see there being much of an incentive to stop flooding online stores with shitty AI-generated books. Because customers will have a hard time knowing what’s good and what’s not upfront.

At the same time, though, customers won’t be happy about this as a whole. Online book stores that don’t curate will stop being useful. Those customers will look for online stores which curate, or for authors on social media.
If you post e.g. on Mastodon, talking about your writing process and all that, people looking for a non-shitty book will take a look.

What you consider successful is an entirely different question, though. Even before LLMs, it was virtually impossible to earn a living wage with writing…

I feel like that’s exactly why we don’t have a generally-accepted definition of consciousness. Western ethics assigns special protection to whatever is conscious, so it is convenient to come up with a definition of consciousness, which excludes groups you want to exploit.

Well, Bethesda isn’t actually involved in that, so it’ll be of much higher quality either way…

Das Krebsrisiko, was von HPV ausgeht, wird um so viel gesenkt. Nicht das allgemeine Krebsrisiko.

Falls jemand bisher nur den Titel gelesen hat…

Will have to play around with it some more, but first experiment was already pretty good. They fry a lot faster than I would’ve thought and do taste better.

Honestly, I’m most excited about this way of preparing them, though, because boiling them first, then frying them, was always annoying. Like, you’d need to really press out the water and need a really hot pan to be able to seer them. And you’d need a pot and a pan rather than just a pan. And if you didn’t wait long enough while boiling, you couldn’t really put them back into the water. And so on… 🙂

Jo, so wie auch so Motorsensen nochmal deutlich nerviger als Rasenmäher sind…

I thought, this couldn’t be true, because surely, one of those cameras doesn’t cost more than like $200. There’s no official price list, but I’m finding numbers online of $2500 per year. This includes maintenance, footage hosting and cell service, which is likely the bulk of the cost. Either way, jeebus, that’s a lot of money.

You might be able to incorporate more lentils and beans. They’re dirt-cheap and fill you up similar to meat.

I always get pre-cooked beans, and red lentils are my go-to for lentils, because they cook quickly and don’t need pre-soaking for reducing their fartiness.

I guess, you didn’t claim otherwise, but just to point out that there’s actually also a genetic change in cultures that have consumed dairy for longer:

In northern European countries, early adoption of dairy farming conferred a selective evolutionary advantage to individuals that could tolerate lactose. This led to higher frequencies of lactose tolerance in these countries. For example, almost 100% of Irish people are predicted to be lactose tolerant.

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

Huh, you fry the dry TVP? Do you then let it simmer in the sauce for as long as one would normally boil it?

I have some steak-like TVP here, which is going to remain dry in the core, unless you really give it its time, so not sure how well it would work with that.

I do also have (pre-)roasted TVP, though, where I assumed, they do that when extruding or something. Maybe they actually throw it into a big pan before shipping… 🤔

I did find it quite weird that the most powerful stage for Digimon was often just a man. Always felt like the, uh, cartoonist(?) had a bit of a superiority complex. Like, what’s more powerful than an iron t-rex? An iron man, of course.

Although, thinking now, there was something about them merging with their humans. Was that just what that last stage is? Then I guess, I would allow it as some dramatic thingamabob.

You’re right that there is a risk, that rebasing introduces compile errors or even subtle breakages. The thing is, version control works best, if you keep the number of different versions to a minimum. That means merging back as soon as possible. And rebases simultaneously help with that, but also definitely work best when doing that.

There may be reasons why you cannot merge back quickly, typically organizational reasons why your devs can’t establish close-knit communication to avoid conflicts that way, or just not enough automation in testing. In that case, merges may be the right choice.
But I will always encourage folks to merge back as soon as possible, and if you can bring down the lifetime of feature branches (or ideally eliminate them entirely), then rebases are unlikely to introduces unintended changes and speed you up quite a bit.

I don’t work with merges, so maybe I’m way off base, but I thought they meant, they’re working on another branch or fork, then merging the base branch into theirs every so often to get the newest changes, and then that creates multiple merge commits, which they can’t squash at the end…?

I’m not sure, about that last part, but the rest, I’ve definitely seen with contributors that didn’t know to work with rebases (and unfortunately we’re on GitHub, which only half-assedly supports working with rebases by default).

I’m guessing, it’s this: https://web.archive.org/web/20120619032849/http://arrangebypenis.com/

Damn, I had a feeling, it was Titanic, because of the eerie lighting, but I’ve never watched it, never seen this scene.

I guess, it did narrow things down, though, that it’s posted here without explanation…

Hmm, well, thanks for throwing that tidbit in either way. I’m certainly not deep into that whole artform, so probably just saw big eyes + cat ears and that was the end of my thought process. 🫠

You might prefer working with rebases + fast-forward-only merges, if you want merge commits to be squashed…

(As in, there won’t be any merge commits. Your PR will look as if you forked, then coded real fast, and then opened the PR before anyone else pushed anything.)