When you try to help, you realize they navigated to this point and then didn't spend 1 minute trying to read the code and see what's going on. I'll take the ot

When you try to help, you realize they navigated to this point and then didn't spend 1 minute trying to read the code and see what's going on. I'll take the other side here... I track my problem to a particular part of a submodule. The person that owns it didn't document it well, didn't write an overview of how the thing works, and generally has made "just reading the code" a poor and error-prone substitute for asking them directly about context they've chosen not to share with anyone else. The person becomes annoyed at my continued questioning instead of "reading the code", and eventually complains about my lack of motivation. The code, meanwhile, never gets fixed, and is a ticking timebomb of technical debt. Whose fault is this? Mine for not "reading the code" and breaking encapsulation, and changing my code to match undocumented behavior? Or the other person's, for failing to behave professionally like an engineer and identify that they are knowledge-hoarding? Who's to say, really. It doesn't matter...I've got another gig lined up.