The problem is more that writing a post that is a list of if you have problem X use solution Y is a nonstarter. People like different things, have different skill sets, and are dealing with a different set of requirements. Finally, it is the sort of thing you would have to keep up to date with the latest version of every framework, language, and OS.<p>To discuss by means of example, lets talk about floors.<p>You decide to redo the floor in your place of residence. Do you:<p>0. Hire it out, using a cheap contractor<p>1. Hire it out, use a vendor in the middle of the quality&#x2F;cost curve<p>2. Hire it out, using the classiest floor shop in town<p>3. Do it yourself, using a rental sander and a youtube video for training, sand your floors down and refinish using stain the guy at Home Depot recommended<p>4. Do it yourself, tear the floors out and replace them from the beams up using reclaimed lumber from the local artists collective.<p>5. Do it yourself, linoleum is fast to install, looks okay, and its super cheap.<p>6. Do it yourself, spend 6 years learning carpentry from a master artisan in the wilds of Scandinavia, fell your own timber using an axe you made yourself, assemble the timber into the master work of flooring using expensive danish hand.<p>Personally I try to do #1 for floors and #4 for software but that doesn&#x27;t meant that works for you. If you have already done the first half of #6 I would be temped to just go all the way.<p>That said if someone gets bored we could do a sort of survey on a timed basis and rate different tools for different strengths ans weaknesses.  Something where you could be like &quot;optimize speed of development versus XML Parsing Quality&quot; and it would give you a nice chart as long as you provide a few quick survey answers.<p>Might Give writing it a try later on. would be interesting to see what metrics people cared about.