Well, I would agree when pilots are careless and negligent.
In the Qatar incident that was not the case. You would have to look at their training and procedures to even begin to see where the genesis of the error occurred. Then you would have to look at human factors issues, such as the major issue of naming the onboard performance tool selection RWY09#T1, meaning temporary notam 1 when there just happens to be an intersection T1 on the very same runway.
This incident is a good case study of why the procedures for onboard performance tool use and data entry must be very robust. It is not in the Boeing FCOM, nor is it taught in standard Boeing courses to check the OPT database runway distances TORA, TODA, ASDA against the charted distances. That simple check, which is practiced by more experienced operations, would have helped to prevent this incident from occurring because then the pilot would have seen the distance that the OPT was using to calculate his data.
Funny, because the first place I learned about this check was on a departure from Doha in my initial B777 training at another operator. The old Doha runway 15 computation in our OPT was for full length. It was very easy to depart from intersection A with full length data because that's the normal departure point and it is the end of the taxiway. To get the actual full length you have to back taxi and do a 180. That plus the runway is 15,000 feet long so it leads to a false sense of security even when departing from intersection A. Look deeper and there is a selection for intersection A in the OPT and compared with the chart you see that it is quite a bit shorter.
Typhoonpilot