Sure. It's a different facet of the same problem. There's a damn good reason that professional software development organizations hire designers and technical writers, and while many developers like to think so, it's not merely to save them time. Developers often suck at making docs for other developers; reasoning about communicating to people one step removed from that gets even dicier. As a developer before I learned good design principles, I often fell into the trap of assuming my being able to assemble something in code gave me sufficient understanding of why it was designed that way. Ah, the hubris of inexperience.