Frog ' s all chill like I ' ll get my revengehUbTDQGM 8 Cg <| sep |> Sorry no click bait was intended . I chose that title because a I thought the Gizmodo title was clickbaity , and b I wanted a title that established a reason for posting this to rprogramming . I found the article very interesting , and went on to read the ESA release and some other accounts . I thought the role that software appears to have played in the incident was really interesting , because as a developer who has worked in aerospace applications , I have been bitten by failing to boundscheck values before using them in calculations . Yes , I know that unexpected IMU saturation was likely the root cause here . But failing to check for saturated values from the IMU before using them to calculate the vehicle ' s altitude , seems to be a failure to bounds check . Of course , until a final report is issued , that may not be true so my title asserts facts not in evidence , and that ' s my mistake . Apparent lack of bounds checking would have been more accurate . There have been some other comments here that bounds checking is specifically for array indexes . I disagree . While that is one of the most common applications of bounds checking , common definitions of the term are much broader . I originally posted the article to rspaceflight , but then felt it would also be interesting to developers , so I looked around for the right sub , and decided on this one . I have no motivation to create click bait and a quick check of my profile will show it isn ' t something I do . I don ' t care about upvotes I just thought developers would find this interesting . I apologize if I named the post badly .