Sure, that's solid policy, but I'm not sure it really addresses the "tribal knowledge" issue per se. I mean, I'd like to think that fixing reliability issues i

Sure, that's solid policy, but I'm not sure it really addresses the "tribal knowledge" issue per se. I mean, I'd like to think that fixing reliability issues increases knowledge, but decades on multithreaded codebases littered with "sleep(0); // just in case" point in a different direction. All I've found to work so far is a deliberate attempt to shift to more active knowledge sharing. I was hoping to learn a few new tricks from OP, but "reliability freezes" are not it, based on my experience.