Originally Posted by
alf5071h
Considering the current views on software problems, does this only relate to the ‘numbers’ (bits), which might have been contained with better choice of software design, or does this also involve an external ‘glitch’, interference or hardware fault.
I don't see it as bad software rather than a bad control design. There are two control laws, pilot and MCAS, that don't “change available information”, uses different actuators and tries to control the same “process state”.
If both works actively at the same time, it is about clear that one or the other reaches some constraint. If it is MCAS pilot feels the pain, if the MCAS wins, situation is much worse.
It will be OK if MCAS kicks only once and then awaits manual resetting. It is just unbelievable that nobody in the Boeing saw the big picture, clearly unprofessional design.