> Also, you sound overly modest to me.
This was my reaction as well. Absolutely no offense to the parent comment, but this sounds like a combination of being overly modest + getting bitten by dumb behaviors by bad companies.
There's also a big difference between:
- Strut into the interview. Drop a copy of your book on the table. "I literally wrote the book - hire me"
And
- "Tell me about yourself" ... "Well, I'm bla bla bla, passionate about xyz, oh, and passionate to the point that I wrote a book about xyz if you're interested in the details"
If you're an arrogant ass, yeah, the book is a liability. But unless you really dislike the thing you wrote and want to squash it, the fact that you wrote a book at all, much less the subject, says something about you as a person. Others in this thread have talked about the positive signals this sends so I won't re-hash those here.
There are multiple problems with that attitude, including: 1) You probably aren't hired to write books, so what matters most is other things you'll be doing. 2) There are really good books and really bad books, so saying you wrote _a_ book doesn't carry the weight you may think. Was it good?
This is true, but some employers will allow you to write on company time. As Kleppman notes, value created by books squirts everywhere, only some of it onto the author, which can be distinct from value landing on their employers.
I've been working on Knative in Action for the last year because Pivotal (now VMware) liked the idea that it would happen under their flag.
(Your books are quite excellent, by the way.)
Donald Knuth Harold Abelson and the Sussmans
- a few others but you get the picture, most subjects do not have a definitive book.
It is not to write code by themselves. It is to help other people do it.
For this, being a walking encyclopedia certainly helps. Of course, there's probably a correlation with being able to solve the programming puzzles in such a situation, too.
