Hacker News Reader

Good advice, but I don't understand why writing a book is the "quickest way to get ridiculed". If a developer wrote a book that provides value, is accurate, and contained very useful code samples, I can't see how that wouldn't increase opportunities.

EDIT: Totally misunderstood that the OP meant it figuratively. Apologies.

View on HN

So I get that you misunderstood the original intent. But that's not gonna stop me from a small rant on writing a tech book. In a word: don't do it unless you really know what you're getting into. Writing an average/mediocre book is a massive undertaking, and if you want to write a quality book, take that and multiply it by 2 and add 20%.

I think he means the expression "Don't write a book" - meaning keep it short and to the point.

Yeah, that's exactly what I meant. If you wrote an actual book on programming, then that's pretty awesome. Writing a book for a résumé, however, is not.

Reply on news.ycombinator.com