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

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

News article: https://en.rua.gr/2024/12/03/loud-arrest-in-moscow-a-robot-drug-courier-fell-into-the-hands-of-law-enforcement-officers/