Did not expect that kind of law change from such an aggressively Conservative government. I guess, there is ample reason to put the NIMBYs into overdrive, though…

Don’t think, Grok was a thing yet back then…

I do feel like AI art has entered the boomer stage of the hype cycle, as in Trump et al use it prominently, so the kids start to think, it’s

.

But I also feel like the blog post conflates two aspects. It’s not just about AI art, it’s also about every goddamn brainfart being turned into AI art.
No one needs to see a t-rex giving a thumbs-up or similar.

That’s what people are tired of, for sure. In the before times, the person would’ve chuckled at the thought and then forgotten about it. It took long enough to create an image of it, that they had time to realize that no one cares.
That barrier is now removed, so you definitely see posts online with just the dumbest brainfart turned into pixels.

I had to start reading that three times over, because I saw they mentioned “Canadian” and just assumed the angle brackets are a joke in reference to the Canadians in South Park:

Did you maybe accidentally turn on the “drunk” mode at the top?

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

deleted by creator

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.

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

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…

Yeah, the big thing is that management has no sense how little coding you actually do in a software engineering role. You spend so much more time understanding requirements, understanding how you can resolve roadblocks within your organization and understanding what the hell the code does that was previously written.

In particular, the last part is something that will most definitely take longer for vibecoded programs.
The code is often needlessly complex, because:

• folks throw in additional features with no restraint,
• the AI will gladly generate a second implementation for stuff, you already solved in the codebase, and
• AI-generated code tends to just be noisy, because you need rigorous logical reasoning to find the most minimal solution.

But you also just don’t have human beings that made all the detail decisions and can tell you why they’re important. In vibecoded code, all of these detail decisions are accidental and only ‘proven’ in so far as the given accidental state that the code is in, happens to not explode in reality. If you need to tweak anything about it, you’re completely blind as to what’s actually important and what’s just in there, because the AI figured, it’s the most likely thing to autocomplete there.

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.

https://en.wikipedia.org/wiki/Canada_goose#Description