Programming crisis : In software programming, can document really help us use the method correctly?
I feel that our current document in software development is not yet systematic enough to allow client code to avoid code violation only by reading document of callees, whether in object-oriented or process-oriented, It is hard to describe the impact of a method on object that is visible to the outside in the document, and the introduction of inheritance and polymorphism exacerbates this problem.