3 ms·
A good read. One of the more interesting, informative and well written pieces to appear here in a while. The one concern I have with this playbook is that fash
by dboreham 10y ago
A good read. One of the more interesting, informative and well written pieces to appear here in a while.
The one concern I have with this playbook is that fashions in niche technical subjects change (I think) very quickly. For this to beat simply selling coding services on a T+M basis the revenue stream would need to continue for several years, with a suite of similar books/courses added over time. Are people still going to be interested in paying money to learn about Ruby performance in 2 years from now? Can two, three, four equally profitable subject be identified and mined every year? Probably not, unfortunately, due to this industry's eternal desire to churn the tech (often to no obvious positive purpose).
- angelbob 10y agoAt his price point, he'll probably get a continual trickle of customers. I sell a book called "Rebuilding Rails" -- not as successful as his, but I've also made a few tens of thousands of dollars, so not nothing. And I reliably make a few more thousands of dollars yearly, years after I wrote it. After Ruby is a "hot" language (years ago), it becomes a legacy language where companies will pay money for assistance with their products. In the $10-$15 niche, you need individual engineers to think a language is neat. In the $40-$10,000 niches, you need companies to think they can save some engineering time. Both can be very valuable.