I enjoyed the article and appreciated the information on ISBN numbers in particular. In addition to the suggestions in the article, I would also add Scrivener

I enjoyed the article and appreciated the information on ISBN numbers in particular. In addition to the suggestions in the article, I would also add Scrivener and Vellum to the list of important writing and publishing tools. For the most part, I think this article is full of excellent advice. I do disagree with three of the author's tips on how to write well though. Specifically: 1. There is no need to avoid alliteration. You shouldn't drown your work in it, of course, but skillfully employing alliteration in your text can help your sentences flow and can make certain aspects of your content more memorable. I'd say it is better to learn to use alliteration, and use it to good effect, than to eschew it altogether. 2. Comparisons are not bad, especially in technical writing. When teaching, it is helpful to tie new concepts to existing knowledge and comparisons are one way to create these mental connections. 3. Generalizations aren't bad in technical writing either, especially in code samples. For example, telling a programmer how to print "Hello, World!" to the screen is a helpful generalization. With that knowledge, the developer can now use that same print statement for console output, messages, debugging, logging, and other tasks. Developers can take this deceptively simple generalization and use it for all kinds of specialized needs. I think the key here is to learn to use alliteration, comparisons, and generalizations in a way that strengthens your writing, rather than detracting from it.