>But listing books on how to do something that's been discussed, and I don't think I'm exaggerating here, millions of times, doesn't seem like you're "helping d

>But listing books on how to do something that's been discussed, and I don't think I'm exaggerating here, millions of times, doesn't seem like you're "helping developers find indie books." Why shouldn't there be indie books about subjects that are discussed frequently? If something has been discussed millions of times, it means that the good information is scattered across several different sources and a lay person has no way of distinguishing between good and bad advice. I've happily paid for indie books in the past few years from authors I trust because I want to read their perspective and information that they've curated. Two I'll mention in particular: Hello Web App by Tracy Osborn - This is a book about web design, which is discussed in millions of places, but Tracy's book gathers together high-quality information in a concise book. Starting & Sustaining by Garrett Dimon - This is about running a small SaaS app. Another topic discussed in tons of places online, but Garrett is telling it from the context of his personal experience running a successful SaaS app for several years.