I think senior engineers should always have good "knowledge gained is proportional to equipment damaged" stories, they're great for helping juniors through thei

I think senior engineers should always have good "knowledge gained is proportional to equipment damaged" stories, they're great for helping juniors through their own "learning experiences". (At my current startup, the one about me and the founder/CTO figuring out how to use an API by experimenting on our only robot arm, resulting in slamming a $30k arm into a concrete wall (mmm, polar coordinates) is great for getting across "you'll be more careful next time, because look, really, there will be a next time!")