While I personally agree that post mortem project discussions are helpful (whether or not the project succeeded), I'm not entirely sure we need a separate section devoted to successful projects.

Typically, this sort of discussion is handled through Meditations. Indeed, many interesting (and occasionally volitile) discussions have been posted about the issues you raise and related ones. For example, consider:

• Productivity and Perl
• Specify, Specify, Specify
• TIMTOWTDI and other languages
• (OT) Finding Technology Solutions
• Why I like functional programming
• On programmer schedules and productivity
• Professional Employees and Works for Hire
• Management that just doesn't understand
• Code Smarter
• Second rate programmers and my confession
• Why our company doesn't use Perl :(
• Experienced programmer - newbie project guy
• Bootstrapping Techies (or how to hire without technical knowledge)
• OT - How to deal with coders who don't do what they should
• And so on...

Admittedly, not all of these are directly related to perl success stories, but they each contain tidbits worth thinking about from a product (and development) management standpoint. This is the beauty of a general category over a highly specific one.

Also, these sorts of issues tend to fall under the aegis of project management, not necessarily direct programming. And there are many, many other sites (and materials) devoted to these topics. A few I can recall off the top of my head include:

• The Pragmatic Programmers (One book reviewed here)
• Joel on Software
• Ed Yourdon's home page (see his articles)
• Extreme Programming
• How Software Companies Die, by Orson Scott Card.

There are, of course, many others. (I should note that I've learned about many of these through reading other nodes, links on other monks' home nodes, and paying attention [when I can] to the chatter.)

In short, I vote against creating a separate section; the one we already have is perfectly adequate. YMMV.

--f