

Well, no, but not every funny story ends with a near-death experience…


Well, no, but not every funny story ends with a near-death experience…


Said first millionaire: https://en.wikipedia.org/wiki/Samuel_Brannan
It’s quite wild. He’s also considered the first to publicize that there is a gold rush, much like these modern AI companies hype up their products to no end.


A bucket of bytes. 🙃
Ah, that makes more sense. I did remember it being a Dutch acquisition.
Dutch cartographers subsequently renamed Tasman’s discovery Nova Zeelandia from Latin, after the Dutch province of Zeeland. This name was later anglicised to New Zealand.


I mean, without knowing the details what your scrum master does, that feels more like a ‘product owner’ role to me.
But to be fair, I’m also not sure, what the ‘scrum master’ role is actually supposed to do. Some say, scrum masters really need to be deeply involved in the whole project to be able to question/assist the way of working.
And then there’s the reality at my company, which is that scrum masters often have 10+ projects, where they just hop between meetings to host them, while hardly being able to contribute anything…


I imagine, this is more about software devs than sysadmins. Sure, you’ll hire a couple more sysadmins to help with the massive user growth during the pandemic. But especially combined with loans basically being made free in the same time, it’s suddenly worth hiring a bunch of devs to build the Next Big Thing™.
Once those loans start costing again and the user numbers fall off, you quickly have lots of devs that you can’t find tasks for, that are worth doing.
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.


Well, Bethesda isn’t actually involved in that, so it’ll be of much higher quality either way…
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).


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.)
Well, the advantage back then was that far fewer cars were on the road…


I mean, even then, they could increase the price per token, if they want to hand out fewer tokens for the price paid.
They could make this work like a prepaid SIM card, where you charge it with e.g. $10 and then you can use it until the $10 are used up.
Instead, they make it work like in-game currencies in scammy free-to-play games. Except that they didn’t choose a confusing conversion rate, for some reason…
Was wondering, if female Canada geese look different from males,and apparently they’re just slightly smaller, but Wikipedia has some excellent info nonetheless:
The honk refers to the call of the male Canada goose, whilst the hrink call refers to the female goose. The calls are similar but the hrink is shorter and higher pitched than the honk of males.


Yeah, I imagine that they did try. But it’s not just the intentionally misleading announcement post, they also have 5(?) different subscription tiers, which get different changes from this. And one of the subscription tiers is actually called “Pro+”, so that does not mean “Pro and more expensive tiers” like I wondered. And they have this ridiculous intermediate currency to make things even more confusing.
Their offering itself is overly complex and confusing…


This image showed up in my feed as pure black and I thought that’s the shitpost, that it’s just all censored. 🫠


Man, they couldn’t have communicated this more confusingly, if they tried.
Hmm, that’s interesting. Don’t you guys generally use concrete for paving in the US? In building construction, you’re supposed to give concrete like a month to fully harden, even though it already looks firm after a day or so.
For paving, they’re likely using a hardening accelerator, so the timelines wouldn’t be the same, but if building construction is anything to go by, it seems like you’d want to give it as much time as possible, not send cars on there while it’s still hot. 🥴