Would having a "license" for companies instead of individual devs make more sense? Imagine Google losing its license to use personal data to target advertisements - this would make them much more sensitive to protecting their users from malicious entities.
I mean, this is a funny troll, but I hope nobody actually packs 16 liters of water for a one day hike. This is a recipe for hyponatremia, a rare yet serious condition of too low blood sodium levels from overhydration.
I don't think most adults should need more than 3 liters of water for a day long hike if they are already properly hydrated. The idea is to hydrate for 24 hours before you exercise. Then during the exercise, you take small sips occasionally. After an hour, you may need to begin replacing lost electrolytes. You also want to drink more often at high elevation and in the cold.
You can actually check how much water you'll need during exercise. Weigh yourself, exercise for an hour, and weigh again. The lost weight is the water you lost and need to replenish.
In any case, you should be peeing every 2 to 4 hours. If the water is clear, you're hydrated. If the water is dark yellow, you're really not hydrated.
To be fair, they do have examples that aren’t chroma keyed; they just lead with one that is.
Which is not to say that ML is necessary for this sort of computer vision task, but I wonder if it yields better or sharper results than other techniques?
Same. As someone who has spent an embarrassing amount of time keying and tracking video footage over the years, I’m surprised ML isn’t being used for this more often in studios by now.
I've noticed that the agile model doesn't work well for a lot of technologies too. Things that have been well studied (for example, creating a webapp with X frontend and Y backend, or creating a graphics engine with DirectX) have known costs and estimates. There are answers you can look up on StackOverflow. Not all realms of technology have such luxury.
Is there an alternative to agile that's available out there?
I am not sure that agile is the right term for what you are both describing.
It doesn't mean releasing things before they are ready. Agile is about potentially shippable increments and customer collaboration. Again this doesn't mean testing in production.
While the manifesto was written for software, with minor changes it can applied to most industries. Even with hardware, agile principles can be used to iterate on design, not necessarily physical production.