Skip to content

Comment on The economics of writing technical booksparent

Comments

My first book C Programing Techniques for the Macintosh was pretty niche. For example, it required third-party compilers and other tools to do self-hosted development on a 512k Mac. But you had to buy it because Apple's documentation had no tutorial content at all, just an API reference.

If you look at Google's documentation of Android now, you don't need to supplement it.

If you look at Google's documentation of Android now, you don't need to supplement it.

Which speaks to the lack of need for books in certain elements of the Android market, but not to technical publishing more generally.

AboutSource Built by g1lg1l

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