I am a pilot, and my complaint is not the lack of a last ditch emergency manual mode, but that there are numerous modes (or alternate laws) in the software abtr

I am a pilot, and my complaint is not the lack of a last ditch emergency manual mode, but that there are numerous modes (or alternate laws) in the software abtraction of fly by wire aircraft, and the plane responds differently to inputs in these different modes, the notification for what mode the system is in has to be inferred, and the pilot is expected to know all of these things. I think it's hubris and incompetence in engineering that a system would be designed this way. And in fact not all of them have these same deficient behaviors, so this is not inherent to fly by wire or automation. It's a choice made by the software abstraction designers. The idea there'd be a mode where advancing a throttle literally does nothing, no increase in power nor a notification that the input received is sensed but isn't going to do what you think it should so that you have a clue in that some other mode is applied, is so totally batshit insane to me. It's a huge betrayal of physics of flight which is something pilots do understand rather well, almost like muscle memory. In a conventional plane, throttle advance always increases power. If that doesn't happen, it's an emergency. In a fly by wire plane if it doesn't happen, it almost certainly means the pilot is confused. And that to me is crap design.