IIRC, the Kinect was supposed to be an integral part of the XB1 package, but was made optional to compete (price-wise) with the PlayStation 4. Pretty unfortunate.
I know that Canada (where I live) has introduced the Air Passenger Protection Regulations[1] in 2019 (and making it better since then), which does have "tarmac delays" clauses[2]. IIRC, we modelled it after EU regulations.
I have my LaTeX resumé on GitHub, and I have a GitHub Action that rebuilds it on a PR, allowing me to see a "staging" version of it. Then it gets deployed to its final destination on merge.
Actually I've used my CV but also its deployment pipeline to sell myself!
> It's easy to forget that 10-15 years ago, the most common dev/ops model was "toss it over the fence"
15 years ago it was often still I without the C, integration that wasn't continuous. Code freeze 1 month before release, put all the bits of code together, everything breaks, try to fix it.
And with the bad (compared to Git) merging capabilities of SVN, last minute merges of feature branches (hurray branchless!) for a release cadidtate to hand over to QA were a nightmare.
I don't know if that's everywhere in Japan but in 2014 I was in Tokyo having lunch outside when suddenly this fast alert (ie. not a slow siren) started blaring, 5 seconds later the ground was shaking.
I did some consulting work for a big Canadian telco, a project to monetize their cell tower data.
It was obviously all tokenized. Not sure if there was any restrictions on who could buy it, but use cases were mostly about knowing how many people were in a certain area (e.g. an outdoor space) and how long they stayed there (e.g. to properly price the cost of billboards).
It's pretty common, afaik, to measure how many pairs of eyes can potential see adverts.
