Nice article, but one passage gave me the willies: > If you’re writing a public API for a library that’s getting exported to the world, or to a bunch of develo

Nice article, but one passage gave me the willies: > If you’re writing a public API for a library that’s getting exported to the world, or to a bunch of developers at your company, it may be easiest to maintain the documentation for that API in code comments. An important idea that I always try to keep in mind when coding is that the me of a few months from now might as well be a different person. All those things I understand so well today, will be no more obvious to me next year than they will for some other person. So I think that if I follow a methodology that makes a distinction between code for me and code for others, then I'm Doing It Wrong.