- how much work do you estimate need to be put for those (a) writing the book and (b) to turning a weak offering into a strong one?
- what is the shelf life of a software programming book?
- Do you make more money by writing the book or by providing consulting for those that want to create content?
Your self-plug in the end implicates that you are more interested in selling shelves than going after the gold.
(b) Hard to say. Some weaknesses (wrong topic) are unrecoverable. Blogging well is way more work than, say, tacking on interviews to an already-great course.
shelf life: longer than you'd think. we wrote ng-book in 2015 and it still brought in thousands last month. (To be fair, I have been releasing updates.)
I don't do consulting. It's the worst of both worlds: the unreliable income of entrepreneurship, but you still have a boss and don't get to accumulate any long-term value.
Re shovels: "If you want to go fast, go alone. If you want to go far, go together." - It's more fun with friends, and we can teach more topics than just whatever I'm an expert in
see also: https://twitter.com/fullstackio/status/1225462654174744576
So I maintain my technical expertise by just asking a lot of questions. It's pretty great because I have a personal tutor to learn some of the most interesting technologies.
Andy Weiss (Fuschia at Google) taught me rust as he wrote Fullstack Rust.
David Guttman (Js.la) taught me advanced Node with Fullstack Node.
Amelia Wattenberger (the Pudding) with Fullstack D3 etc.
Having such awesome personal conversations - that were essentially lost to the ether - was actually the inspiration for us to launch our podcast: I just wanted everyone to learn what I was learning.
Edit: you're not your
We're sort of the inverse of Web Development (programming) fatigue. We'll run out of products when developers stop creating new web frameworks (and programming languages and platforms and and)