There is no assumption of privacy when operating heavy machinery. You are quite literally wearing an identification tag on the vehicle at all times, such that you can be identified in the case of violating rules.
Speed cameras are good, actually. As mentioned in the article, speeding was reduced by 71% at the installation sites.
So is using design to manage speeds - also mentioned in the article.
You can't really use a speed bump on higher speed roads, where speed cameras can be a good choice to enforce speed limits.
Strategic use on roads with a desired speed around 70 km/h around areas with collision risk is a good use-case for speed cameras. This is how they are often deployed in Sweden - you put up a sign warning drivers that a speed is imminent, and compliance with the speed limit becomes essentially universal. A drop in crash risk follows.
Using speed bumps and roundabouts is also obviously good, but they serve different use-cases.
Speed cameras are a form of enforcement - you exceed the speed limit, you get a ticket. Quite literally the definition of enforcement.
I want to remember being fingerprinted at a Canadian airport the one time I had a layover there in 2018.
This is all pretty common these days.
You enable it using git config, after that it will apply to whatever frontend you're using.
Depending on how structured your commits have been, it can either be very difficult to get a rebase through or a complete breeze. There are some features to make it easier - rerere being the main one I'm thinking about.
This particular station is unusually minimalistic for the Stockholm metro.
For an example of what I would call a more spectacular looking station, check out this photo of Rådhuset: https://stockholmartwalk.se/guide-to-the-art-of-stockholms-subway/the-history-of-the-art-at-radhuset-metro-station/photo-location-5/?lang=en
Hötorget station. A particularly confusing one to understand the exits, I never seem to be able to get out where I want.
What's your mental model for a Git commit, and a Git branch?
Once I properly learned those two concepts, understanding rebases became a lot easier.
I'll try to explain it to the best of my abilities.
When you rebase a particular branch, what you're essentially doing is taking all of the commits that are currently on your branch, checking out the other branch, and then applying each of the patches in order on that new branch.
A rebase can be cleanly applied if the premise for each commit has not changed when applied, but if the premise has changed, you get a conflict to be resolved before being able to continue the rebase.
I mentally model a rebase a bit as a fast version of how it would look like to build the branch I was on, but on top of the branch I'm rebasing on.
ps aux | xargs kill -9
If you're not using the toilet brush, please start doing so
Provide him with some socialized housing in the form of a jail cell