• 0 Posts
  • 36 Comments
Joined 16 days ago
cake
Cake day: April 20th, 2026

help-circle





  • 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.



  • trem@lemmy.blahaj.zonetoLemmy Shitpost@lemmy.worldCure
    link
    fedilink
    English
    arrow-up
    5
    ·
    4 days ago

    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


  • trem@lemmy.blahaj.zonetomemes@lemmy.worldEvolution
    link
    fedilink
    English
    arrow-up
    8
    ·
    5 days ago

    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).