Live data from Hacker News

Writing a book: is it worth it?

martin.kleppmann.com

91–100 of 299 posts

Re: Writing a book: is it worth it?

#91
post #77

My favorite line in the post, and one that inspires my own efforts lately: > How to be a 10x engineer: help ten other engineers be twice as good. Producing high-quality educational materials enables you to be a 300x engineer.

Writing a book does not add value to your employer, enabling engineers in the world is one thing but it does not affect your day to day job or people arround you.

yes, why would an employer want employees who have the capability to write a book on the payroll? That's time that could be spent heads-down coding!

Re: Writing a book: is it worth it?

#92
I'm a software engineer and the author of four books, but none are about software. (Three are pop-sci and one is pop-stats.)

First book (2013) did extremely well and continues to sell well. Lots of good press, translated into multiple languages, excerpts in a national magazine, promotion on a network TV show. Second book (2014) tanked hard. Third book (2019) looked like it would suffer the same fate as the second, but sales have been slowly inching up. Fourth book (2020) has seen abysmal sales, likely because of the pandemic, but it's a direct sequel to the first book and there are opportunities for cross-promotion, so I'm hoping sales eventually pick up.

I've been fortunate that throughout the course of writing these books, I've had a full-time job that pays the bills, so any advances or royalties have been gravy.

But if I could give advice to those who are interested in writing a book, it would be this:

* Unless this is purely a vanity project, do not go in the red. I would not have written my books if I hadn't gotten book deals. I wouldn't have put myself in the red by hiring an editor, a proofreader, an illustrator, a designer, a publicist, etc., which is what you likely will have to do to produce a quality book when self-publishing. A "you have to spend money to earn money" mindset is not the best mindset to have in a category where relatively few books succeed.

* Publishers these days aren't looking for good writers or great writers. They're looking for marketable books in established categories written by half-decent writers with solid platforms. There are certainly exceptions to that, but you can't hurt your chances by strengthening your platform or doing your own market research before even approaching an agent. (By platform I mean a built-in audience -- people to whom you can market the book. For better or worse, this means having lots of newsletter subscribers, YouTube subscribers, a big social media presence, blog readers, etc.)

* If you are an introvert, you will likely find being an author uncomfortable. You might have no problem with the often solitary task of writing the book. But the hardest part (and potentially the most time-consuming part) of being an author is not the writing itself but the marketing and promotion that comes afterward. Don't expect to be able to lean on your publisher for this. After a brief promotional blitz around pub day, you're likely on your own.

* There is a quote attributed to a number of famous writers: "I hate writing, but I love having written." I can all but assure you that if you're working on a book of any decent length or depth, you will reach an "I hate this" moment. But once the book is published, for the rest of your life you get to say that you're an author. It's a pretty cool feeling.

Re: Writing a book: is it worth it?

#93
post #88

Very different experience for me. Wrote a book about Redux ( https://leanpub.com/redux-book ) brought about $15K for 4 months of work. (Granted, did no marketing at all) It always feels strange to say "I wrote a book" and it never seemed to really impress tech people or cause an inflow of consulting work. But it is very fun and you get to really get into the tech (other projects, sources, blogs, testing ideas). Prob…

Do you think the lifespan of the topic or the delivery platform impacted your returns? I don't buy a lot of books anymore but used to drop 40-50 bucks on an O'Reilly book that would be used for years. My LP purchases probably top out under $10 and are for more immediate, short-lived topics (which seems to be what the platform targets with it's digital & updated content focus)

Re: Writing a book: is it worth it?

#94
post #76

Earlier quoted context omitted.

I'm pretty sure if I showed up to a performance engineering job interview and said "I wrote the book on performance," as though that was what mattered most, I'd be shown the door. In my opinion it would be horrendously arrogant. In fact, I interviewed at Google while I was writing Systems Performance for Prentice Hall, and I never mentioned it in the interviews for that reason. In such interviews I'm focused on what…

A prototypical Hacker News reply.

I don’t think you realize who the author of that reply is.

There’s nothing HN typical about him :)

Re: Writing a book: is it worth it?

#95
post #44

He kind of touches upon it, but there is a lot of value in being able to go into an interview and literally being able to say about a topic "I wrote the book on it." It's a tremendous signal to have overcome the hurdles of getting a publisher to accept you and print your book with your name on it. I used to have several guys on my team that had published books- and they were great, and were constantly getting contact…

I'm pretty sure if I showed up to a performance engineering job interview and said "I wrote the book on performance," as though that was what mattered most, I'd be shown the door. In my opinion it would be horrendously arrogant. In fact, I interviewed at Google while I was writing Systems Performance for Prentice Hall, and I never mentioned it in the interviews for that reason. In such interviews I'm focused on what…

To give a different perspective: I co-authored a technical book 19 years ago.

It is listed on my resume, but i don’t mention it at interviews because it was so long ago.

Last year at a job interview, the interviewer told me he still had my book. I got the job.

Re: Writing a book: is it worth it?

#96

Earlier quoted context omitted.

I'm pretty sure if I showed up to a performance engineering job interview and said "I wrote the book on performance," as though that was what mattered most, I'd be shown the door. In my opinion it would be horrendously arrogant. In fact, I interviewed at Google while I was writing Systems Performance for Prentice Hall, and I never mentioned it in the interviews for that reason. In such interviews I'm focused on what…

Sounds to me like a good way to weed out bad employers. If they think of a book as a negative, they probably have a few chips on their shoulders. Also, you sound overly modest to me.

Disclaimer: I haven't written a book.

> 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.

Re: Writing a book: is it worth it?

#97
post #84

Earlier quoted context omitted.

Sure. But the skill remains in competition with all other skills --- some specialisation or specialisations must shrink for another to grow. With a century of universal compulsory education, US adult literacy rates have difficulty cracking 91%.[1] That's about 10 million people with no effective English literacy. (Some are literate in other languages.) Some other industrialised countries see similar results, though m…

The shift in skills tends to be advantageous to the new experts not the old ones. The great books on using slide rules have already been written, but their unlikely to find a new following. Java applet‘s and a host of other tech is simply not coming back. Which is why experts often become advocates, they want their skills to remain relevant.

If one presumes a culture with an increasing overall complexity level, then the circumstance is not one of simply obsoleting technologies and skillsets being replaced, but of competition among multiple essential skillsets.

Complexity expands to meet all constraint boundaries.

Re: Writing a book: is it worth it?

#98
I wrote a book once. I could do it again, but I haven't found a reason. It's a hell of a lot of work.

I think one thing that helps, is to have a "timeless topic." People still read Knuth's stuff, and Steve McConnell's Rapid Development is just as valid today, as it was, 25 years ago.

Re: Writing a book: is it worth it?

#99
Martin Kleppmann is a great speaker, if you have a chance watch any of his talks on youtube.

The book itself is also great, it gives an amazing lay of the land when it comes to databases / database methodologies and algorithms.

Re: Writing a book: is it worth it?

#100
post #92

I'm a software engineer and the author of four books, but none are about software. (Three are pop-sci and one is pop-stats.) First book (2013) did extremely well and continues to sell well. Lots of good press, translated into multiple languages, excerpts in a national magazine, promotion on a network TV show. Second book (2014) tanked hard. Third book (2019) looked like it would suffer the same fate as the second, bu…

> solid platforms

Can you expand on that?

Very interesting comment, thank you!

Post reply on HN