And yet... haven't you noticed that supermarkets in posher areas are less likely to have the coin slot? (Asda and Tesco are two whose policy varies by location).
And in supermarkets with large car parks there are return stations all over the car park. Which means you still need to pay trolley herders...
For me the "minimal set" of rules that can still be called Agile is a mechanism for measurement, and a retrospective. You use the retrospective to perturb the process, and you use the measurement to decide whether that perturbation was a success or a failure.
That's it - old school cybernetics. If you used feedback loops to iterate towards a successful process, you're doing Agile. If there are parts of the process that are off-limits to you (eg management insists on doorstepping your standups) then you're not doing Agile.
Of course, we "prime the pump" somewhat by throwing in a bunch of extra rules at the beginning that we know from experience are likely to work, but I think that Agile, done right, has a lot in common with Nomic.
If your purpose is to allow the device to be used when it doesn't have your full attention - like a car radio, for example - I don't think that's a good solution.
I have a phone with a knurled power button, and a smooth flashlight button next to it. It's a minor example, but dynamically remapping those buttons would destroy a lot of their utility for me.
Thing is, I had that all set up! I'd deleted all the IE icons! Spotify did an end-run around all my precautions, because there was basically no way to remove IE from the OS, and any app that wanted to use it could.
Years ago, a Windows virus slipped on to three family machines I'm the go-to-guy for, due to Spotify using IE to display ads, and not vetting its ads properly.
My answer was two-fold - never use Spotify, and always use an ad-blocker.
Putting aside the difficulty of building that database of true facts, and of parsing unknown facts out of English text, that solution feels like it's inviting an arms race. I can write a bunch of uncontroversial "true" facts into an article containing one or two false facts.
"Use a bouncer" might be the answer there. All engineering is compromise, and needing a bit more compromise to support legacy applications is not unreasonable.
(In fact, why are you running a stream-oriented application over such an unreliable connection at all?)
Well he was replying to me and I didn't read him as uncivil at all.
His response ("syncing is expected") is completely on-point when talking about the PoLS. I disagree, obviously, and think syncing is scary voodoo magic. I don't see how you can say "users are unsophisticated and don't understand the difference between web sites and web browsers" and also say "users are sophisticated and expected config syncing".
Unfortunately, to get any further we have to test users.
We could apply the principle of least astonishment to get a feel for correct behaviour without resorting to sterile arguments about what proportion of users understand the difference between a web site and a web browser.
If they looked at a slightly risque URL on their phone, would the average user expect Chrome on their laptop to autocomplete that URL?
There's got to be something that grows faster, and is easier to sequestrate, than trees. Bamboo, maybe? Seaweed? Algae? Dry it off in salt pans and dump it in the deep, cold ocean?
That's just dumping more carbon into one of our natural sinks, I think, rather than trying to create a new artificial sink. Even just using it as fertilizer has got to be an improvement over using inorganic fertilizers.
And in supermarkets with large car parks there are return stations all over the car park. Which means you still need to pay trolley herders...