Team 548 Einstein Statement

[Nick Lawrence]

Remember, FIRST did not cause this. It was a bug in the newer Field AP firmware that created this security hole.

-Nick

[Siri]

I just wanted to thank 548 for taking the courageous step of publishing this piece. Having committed no fault of their own, they've admirably given our community further impetus to move past the individual's conduct and embrace the challenges and opportunities this situation has exposed in our future. We owe it to ourselves honor just that.


I am impressed with the general tone of this thread in this point. I hope our students --and adults -- can continue to learn from the commendable behavior of 548, all the Einstein teams, and everyone involved in the invetigation. (Certainly some in their echelons may still be recovering, but hopefully this helps the process on tragically affected teams.) I know I will work to develop and retain this culture change, and while I hope we can avoid or preempt such incidents in the future, I believe we'll be better equipped as a community if we must handle one again.

[Ian Curtis]

Originally Posted by Nick Lawrence

Remember, FIRST did not cause this. It was a bug in the newer Field AP firmware that created this security hole.

-Nick

If your car breaks, do you blame Delphi? Unless you are a huge car dork or work for an OEM, probably not. There are plenty of examples in modern industry where the supplier is the cause of an issue, but everyone still points the finger at the final assembler. Since it is your brand attached to the final product, you've got to ensure that you want your brand on it, even if you didn't build all the parts (and these days, no one builds all the parts).

Originally Posted by SuperNerd256

What he/she did was a good thing at the wrong time, the worst time.

This is absolutely a bridge too far. Ethics are important.