It's not a bad idea, but I'm not sure we necessarily need another area. Certainly any code post could contain commentary, in the form of comments or even POD.

Also, many monks provide extensive details in their more-thought out posts. Consider Ovid's Death to Dot Star! or chromatic's Common Regex Gotchas. Also, Dominus's home node provides links to his site, where he's mirrored many of his articles.

It takes a special combination of skills to be able to explain code and to craft it. These skills must be nurtured and deeloped if you're going to gain any decent respect from your peers. Or, at the very least, any respect from the person who has to maintain your code.

In other words, it's a discpline thing, a skill you'll develop as a programmer. Feel free to document your code as completely as necessary--especially if you're counting on bits, behaviors, or sublties of the language that might be confusing to inexperienced coders or lesser mortals.

In short, we should already be doing this, save perhaps in Ob-Fu, where working through the confusion is the learning exercise.

--f