I always wished the throttle to be linked to slip sensor on wheels, say push back throttle a bit more when the wheels start slipping and not just wonders why WOT doesn't accelerate as fast as usual all while ECU is pulling power because of slip
We had users complain about migrating to MS Teams as the text part of it is almost entirely a piece of shit that every competitor does orders of magnitude better but management said "fuck it, we're migrating regardless", throwing oh-so-great arguments like "our customers also use it"
Only if you're extremely dishonest in comparisions.
Checklists at its core is just a list of common/required actions grouped in a list to don't forget during routine tasks. There is nothing limiting here, it is just a tool to aid repetitive/rare/complex tasks.
Exactly. The checklist has no endogenous enforcement capacity. The software defined world is wholly different.
“In a fully developed bureaucracy there is nobody left with whom one could argue, to whom one could present grievances, on whom the pressures of power could be exerted. Bureaucracy is the form of government in which everybody is deprived of political freedom, of the power to act; for the rule by Nobody is not no-rule, and where all are equally powerless we have a tyranny without a tyrant.”
That's also easier way to design it in Factorio. When I was playing with Space exploration mod that's precisely what I did, the base sent "shopping list" and the provider sent stuff on that shopping list
> 1) Robust system design involves identifying the parts of your system that are mission-critical and always monitoring them. NASA missions have great automation and a 24/7-staffed mission control.
You should alert on critical parts but you should monitor anything and everything you can. It might be critical in finding out why system broke later on. Easier said than done for hardware but easy for software
The buggy behaviour of A caused buggy behaviour of B that caused buggy behaviour of C, just so happened to align enough to "look like it is working".
Double fuckup if the thing is backups and your data is gone. Reason why we check not only "does the backup job finished" but also "does the size looks right", because backup with 0 files still returns OK...
Haha yeah, been there. I forget all the details, sadly, but there was some long-present bug with how the frontend architecture word in the dev environment that would keep the changes from being propagated. But every member of the team had set up a workaround so that, on their machine, it would load the correct assets some other, undocumented way, so they wouldn't notice the bug.
> For example, cars have "fail open" brakes but have independent cylinders so that it is relatively hard to have all four wheels fail at the same time (older cars had single master cylinders) - and one of the tradeoffs is that people want cars to get going immediately and not wait for brake cylinders to "charge up".
And emergency brake that's wholly separate circuit.
