3 ms·
Right; the person saying "I literally wrote the book - hire me" is saying it matters most, and I think that approach is likely to backfire. There are multiple
by brendangregg 6y ago
Right; the person saying "I literally wrote the book - hire me" is saying it matters most, and I think that approach is likely to backfire.
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?
- bryanrasmussen 6y agoI think the problem is for most technical areas and for most technical books the writer has not literally written THE book on the subject, they have at best written A book on the subject - of people who have written the book on the subject I can think of, off the top of my head: Donald Knuth Harold Abelson and the Sussmans - a few others but you get the picture, most subjects do not have a definitive book.
- jacques_chester 6y ago> You probably aren't hired to write books, so what matters most is other things you'll be doing. 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.)
- cnst 6y agoThe main difference is the reason that a senior engineer or VP gets hired. 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.