Should you write a book?
Many “should” questions can be answered with a technique that’s hundreds of years old.
Between inventing bifocals and being the first technical content marketer, Benjamin Franklin is recognized as the creator of the Pro/Con list.

Here’s how Franklin described it:
Divide half a Sheet of Paper by a Line into two Columns, writing over the one Pro, and over the other Con. Then during three or four Days of Consideration I put down under the different Heads short Hints of the different Motives that at different Times occur to me for or against the Measure.
Are you thinking about writing a book?
You opened this email, so there’s a good chance you might be interested…
It could even make a lot of sense to connect with your technical audience.
So, grab a piece of paper and divide half with a line like ol’ Ben describes.
On the pro side of your paper, you might write:
- Be seen as an expert in your topic
- Open doors to conferences and other events
- Use the book as marketing for a product (or yourself)
- Finally become an author
And on the cons side, you could jot down:
- You dislike writing
- No clear connection between the topic and your work
- You aren’t sure you’ll finish the book
After deep consideration, perhaps seeing these two lists will help you make the right call.
You might also have other questions, such as whether you need a publisher or a print book. I answer those in my post, Self-Publishing as Technical Marketing.
Get your tool shortlisted
One short read a week you can use to better understand developers and the LLMs that drive their work.