|
|
|
|
|
by Swizec
718 days ago
|
|
Yes, don’t write technical books for the money. But also do! If you approach the book as a business venture, there’s plenty of money to be made. Here’s my recap of making almost $400k over a few years of working on books-and-such as a sidebiz alongside a full-time job. Not all of it was from books directly, a lot was from opportunities that the books unlocked. And that’s not even counting how the books enabled me to sponsor my own visa/greencard to come into USA and unlock oodles of opportunities. The main insight I’ve learned is that the book is a product. Write your thing for someone to benefit from. What [useful thing] will they be able to do after reading your book that they weren’t able to before? How does it help them get more of what they want faster? https://swizec.com/blog/5-years-of-books-and-courses-or-how-... Sharing this to encourage, not to brag. We need more insightful and useful books out there. If you’re gonna do this, I strongly recommend picking up a copy of Write Useful Books first. Wish it existed when I started. http://writeusefulbooks.com/ |
|
My pet peeve is indie dev influencers who tweet “anyone can do it” while ignoring their own built up momentum. I don’t know enough about you to ascertain either way.