Skip to content

Comment on Ask HN: Would you read a statistics textbook?

Comments

Practical advice:

- put a lot of 'teaching' into the book. Don't write so the learner memorizes; instead, motivate each discussion so that the learner understands, and gains what Wirth calls _coverage_.

- ensure there are no errors; this will turn off learners.

- keep a light tone, be yourself not a stuffed shirt. A good model for such writing is Nassim Taleb's non-technical books.

- never seem to be in a hurry. Many good books were ruined because midway the author lost interest and just hurried up.

- don't be too verbose, and neither too concise. Every sentence should do required work; learn how to write (if needed) and practice daily.

- ensure the book uses good, comfortable fonts, and good typography. Must learn this. Many good books ruined due to lack of fluency effect.

If you conscientiously do these things, there will always be readers for your book.

Good luck!

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.