> do not teach non-technical people how to make a software business (expected success rate of people who buy that book: < 1%, if that) [but for example] write t

> do not teach non-technical people how to make a software business (expected success rate of people who buy that book: < 1%, if that) [but for example] write the book on Ruby on Rails developer integration testing, there is at least a 50% chance that I will be at least somewhat successful You need to have certain ratios to give that advice. For each Ruby on Rails developer who wants to learn about integration testing there are probably 10,000 non-technical people wanting to break into the software business where there think that they can becomes software millionaires working part-time in their basement. So, bigger audience for the latter book. On the other hand, for each book about Ruby on Rails integration testing, there are probably hundreds of books that teach non-technical people how to make a software business. So, more competition for the latter book. I don't know the ratios involved. Unless you have actual statistical information, I think we're both just speculating about which might be the better strategy. I'd much prefer to write a good technical book rather than delude non-technical people into thinking they can become software millionaires. But looking at the cold hard rate-of-return, I don't know which makes more money.