Skip to content

Comment on The economics of writing technical books

Comments

There’s a hack if you work in Developer Relations for a tech company.

1. You write the book as part of your job during the workday. 2. Your company buys the published book to distribute at events and conferences for free. 3. The book seems successful and you get paid. 4. The book gives you credibility in industry events and may even help you get a special visa if you need one.

Full disclosure: I have never written a technical book, but you should if you work in Developer Relations.

AboutSource Built by g1lg1l

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