There are two other solutions, make the automation so reliable that the human skill is not needed, or make the consequences of failure low enough that you can just accept failure.
As far as I know, Places that actually care about safety apply all of them at once.
They add layers of failsafes that don't rely on humans, they make the automation better and better, and for the most critical stuff, they continue training for things that will almost certainly not happen.
And for the rare(depending on personality) cases where we care about the pilot's ability more than the result, just don't automate at all.
Not an app, but a productivity system, partially refined by telling AI every time I forgot anything and asking for research references on human error that are relevant to that specific mistake:
I've been doing LARP and tabletop most of my life, that's exactly the feel I was going for.
Most of the actual functional "backend" parts come from computer science and various research used in safety critical industries (Like Crew Resource Management), but the general aesthetic is heavily tabletop influenced.
I haven't done much with most of the explicit "gamification" elements like habit trackers use, because those usually don't actually feel like games, they're mostly just performance metrics without any story or gameplay mechanics.
I think it would be cool in theory to have some sort of XP system, but mostly everything I've seen seems too much like bookkeeping overhead.
In real TTRPGs, the points actually represent something, but with habit trackers, they're representing results that already exist automatically in the real world as a consequence of the habit.
I can't imagine that mics are going to be affected by anything that doesn't also seriously bother at least some animals, definitely not something I'd use outside of some ultra secure conference room or something.
A web based inventory management app. I've wanted to try something like this for a long time, but it always seemed completely impractical to spend a few weeks on before AI, without knowing if the entire idea is actually practical.
So far, I think it is in fact worth it, but only in specific use cases, like very rarely accessed items with no obvious place, and making sure your AV gear you bring to events comes back with you.
* Every item is a container, unlimited nesting
* Everything stored in the browser with YJS, very clunky peer.js or manual file sync available
* Select an object, click add items, scan QR codes to add those items
* There's also NFC support on Chrome mobile
* Generate random printable QR sheets(Still need to fix sticker alignment issues)
* Tracks where an item was last scanned with GPS
* Save container contents as a loadout, check contents against loadout
* Can mark a container as needing re-inventory, contents that haven't been re-added after that show a warning
I remember doing my own backups with rsync a super long time ago! It worked pretty well, but it didn't have compression, encryption, desktop integration, or deduplication, and adding anything would be one more script to maintain.
Now I use Kopia, no real complaints there. I used to use Borg but until recently it needed some fussy extra community package to work on Synology.
Something future proof for new chemistries, consumer friendly and self protected, able to be series-es and paralleled if needed, etc.
Maybe even designed to be an external part of the case like 2 way radio and tool batteries, with the option of a retaining screw for toys and tamper resistance.
A few different sizes, from keychain up to power tool, and paralleling adapters to go bigger.
The electronics would probably cost pennies in volume, just like the tech that goes into those lithium AAs with built-in chargers and buck converters that are almost really awesome.
I've been using one folder per client, one folder per project for years, with no issues, although I don't tend to work on small pieces very often, I rarely do anything that seems too small to make its own project folder.
I used to do the FHS style organizing things by category, but now I'm pretty strongly against non-isolated project environments.
Sodium ion showed up a year or two ago and you can buy them on Amazon as 12v lead acid replacements, 18650s are also available but the voltage range is different from normal lithium.
As far as I know, Places that actually care about safety apply all of them at once.
They add layers of failsafes that don't rely on humans, they make the automation better and better, and for the most critical stuff, they continue training for things that will almost certainly not happen.
And for the rare(depending on personality) cases where we care about the pilot's ability more than the result, just don't automate at all.
reply