4 ms·
You’re not seeing the parallels. The original comment suggested recording every action from the cockpit and using it for analytical data. The final action isn’
by abadpoli 3y ago
You’re not seeing the parallels.
The original comment suggested recording every action from the cockpit and using it for analytical data. The final action isn’t the goal. The steps and discussion that got them to the final action is. Hence recording every step the pilot takes, and the equivalent would be also recording every discussion that the software developer made that influenced them to write the code the way they did.
Saying “the git commit is there, that should be good enough to know the result” is like saying “the pilot landed the plane, that should be good enough to know the result”. Why do we even need CVRs at all? The final action is right there, right?
So again, why record everything the pilot says but not everything the developer that wrote the autopilot says?
- deleted 3y ago[deleted]
- Aeolun 3y agoI think it would be helpful to qualify ‘everything the pilot/developer says’ with ‘in the past 25 hours’. For a pilot that just flew a 12 hour flight with a malfunction that would be of obvious benefit. For a developer that introduced a bug 8 months ago, maybe not so much. Even if you recorded every interaction the dev had over that time period nobody would be able to go through everything and get sensible information.
- abadpoli 3y agoThe comment that kicked off this chain of comments wasn’t suggesting the past 25 hours, it was suggesting recording all flights, always, and storing it forever to be analyzed at any date in the future.