It has also been my experience that engineers tend to dismiss these sort of problems as 'finger trouble' on the part of the pilot. If the machine & it's computers are designed not to do something, people find it hard to accept that it can actually do the very thing it was designed not to do.
We had a omega nav system that would display and indicate us on a track that was in the opposite direction to our planned and actual track. The catch was that it only happened from one location that we flew out of on a weekly basis. The fault did not appear at any other departure points The manufacturer said it was impossible - could not happen.
If the unit was reset after departure it would then work fine.
Trouble was we could replicate the fault on every departure from this particular location. We recorded the lat.long readings over several flights and passed them on to the manufacturer. They asked for the unit and we received a new replacement unit.
No explanation was forthcoming.
So software can have hidden bugs that the developers cannot foresee.
How many time have you sat at a computer and wondered "why did it do that"
A pilot will to react in a particular situation an a certain way, based on their training, knowledge and experience. A computer programmer may have the knowledge to program a system for x number of foreseeable events. But as we know there is always a situation that comes out of left field you will need experience for.