I've been on both sides of this. Stuff happens. Even the best processes can sometimes fail. Comments here have been pretty spot on. Reviewing what went wrong and actually putting procedures in place to prevent it in the future is about all you can do.
Of course, you said, "due to recklessness". Keep in mind, "recklessness" is completely subjective. A great developer could be under a lot of pressure to get something out the door. Where does that alleged recklessness come from? Just some sort of lapse in judgement? Or, perhaps, working against the clock to get something out the door due to overselling and underestimating on the part of management. Or was it just developer burnout... working long hours to finish a project or fix critical bugs or whatever, and the developer was simply exhausted?