This is the 3rd attempt at writing a helpful, yet concise post, and I think in actuality your comment is just as much help for Oscar as the 3,000 words above it are for
the technical side of the booking.
Not exact matches
Once I settled on the
technical side of things, I started reading
books about
technical analysis.
I have read many
books on the
technical side of this great sport.
I would love to be able to recommend a single
book to a novice instructional designer that covers both the design and
technical sides of eLearning development.
Though there is nothing wrong with knowing the
technical side of making a novel, I think it is wise that you would let someone do it and just focus on the marketing
of your
book.
Your time is better spent working on new manuscript ideas instead
of spending hours tweaking layouts and formats or even worse, having to learn the
technical side of everything associated with promoting your
book.
I have some problems with the
technical side of it, from some problems that Amazon refuses to address, and I dislike that Amazon had to look in on readers to see how far they read to determine that payment (I often delete a
book after I finish it, since I have loads on my Kindle at any one time and I rarely sync the device; does someone doing that with a loan mean we don't get paid?).
I'm not a huge fan
of the
technical side to publishing a
book.
Before you get to the
technical aspects
of uploading and publishing your
book, consider the strategic
side of the process.
As for
books to learn from, Andreas M. Antonopoulos» Mastering Bitcoin is a fantastic introduction to the
technical side of things.