> that an engineering that's "been there, done that" can foresee the needs ... Agreed. That said, where I've encountered the most issues have been when engine

> that an engineering that's "been there, done that" can foresee the needs ... Agreed. That said, where I've encountered the most issues have been when engineers who are relatively new hires *believe* they've "been there, done that", and haven't yet internalized the different nuances of the situation vs their prior experience. This sets up a dangerous scenario where they have enough experience to be quite believable, but unfortunately may be missing the fact that their experience isn't as applicable as they believe.