| hmm very interesting. So can I write a book on any technical topic or programming languages only? Like I am / wish to be involved in some projects but they are sparsely related , maybe I can apply the pareto principle to see what is a good balance of my interests and what pays / there is demand for. My main nut which I like to crack is breaking nat's. It drives me crazy when I can play a minecraft server on nats.
But I also don't want to reveal such things because they work because I spent hours tinkering and if I tell to the world , it would take the nat owners just minutes fixing it. But still , I don't know , I was thinking of creating an article because book seems pretty heavy. How long does the book have to be , can it be a 50 75 pages long ? or does it have to be insanely bulky like 1000 pages ? Sorry if I sound a bit immature because I totally am. I always used to think of blogs as a way to increase my reputation but now I am thinking why not both ? the topics I am good at , can really be both blog / article and a mini book. Should it be digital or should it be by a publisher ? |
I created a course about technical book authoring and interviewed a dozen authors. Some made a lot of money from writing. Others less so. Those that treated it like a business seemed to make more money (from the book and related activities).