The past few years have seen a venerable explosion of self-published ebooks.
Might be that e-book readers are becoming ever more popular, or that people actually buy ebooks. Whatever it is, this is a good time to get your act together and write a book on something you're good at.
Or even not good at. There's a guy who will research any suggested topic and write a book. Naturally, I can't find the link right now because "I will write a book about anything" is a terrible search term.
But what's a guy to do once a topic has been identified?
Creating an ebook takes plenty of strange knowledge about file formats, layouting and making sure this book looks equally good on an Android phone as it does on an iPad or a Kindle. Let's not forget the book will eventually need to be sold - you need a website, a landing page, some marketing, optimizing conversion funnels, some way to send emails to buyers, processing payments ...
Blah. All I wanted was to write a book!
Plenty of services exist that help you out with everything around your book, so you can focus on the writing (and marketing, self-publishing means you do the marketing). My google-fu revealed Leanpub as the best option. My experience so far tends to agree.
Leanpub
Leanpub is an ebook self-publishing platform with an interesting twist - it encourages authors to treat their books as lean startups.
The idea is to eschew all the crap that comes with writing a book for several months only to discover nobody wants to read it. Instead, you write the first nugget of a book and start selling. When you write more and the book matures, updates are pushed to all your readers for free.
Essentially people are paying for a future full book, but getting a taste of it now.
Two things happen:
- You get continuous feedback and can adjust the course of your book at any point. In the end you will almost certainly have an awesome book.
- The accountability of everyone watching you means you won't just give up after three chapters. A fate too many of my early book attempts have endured.
I also really like the book creation process.
Writing happens in simple text files with markdown syntax. These are stored in a shared Dropbox folder so when you want to generate a new preview or publish a new version, Leanpub will simply sync the files from your computer and do its magic.
They also have great customer service - the founder is always prompt to answer any questions on their mailing list - the writer dashboard is marvelous and they let you download any data in a csv format so you can do whatever analysis of sales you might want.
Oh and coupon creation and so on ... they also handle all the mailing. Seriously, everything you need around your book, so you can focus on the writing.
The real killer feature is their TOS. Authors retain full copyright, there are no restrictions about using other publishers, no restrictions about selling the book without cutting Leanpub into the deal and so on. At 90%-50c the royalties are also very generous compared to more traditional publishers.
Compare this with a traditional publisher contract I read last night; give away all copyright, both moral and practical, only allowed to quote your book according to fair use, must always mention publisher when talking about book, 16% royalties, indefinitely allow them the use of personal trademarks like my name for any purpose they deem fit, and not even a promise I would always be mentioned in relation with the book in question etc. etc. ...
No no, Leanpub is universes ahead of traditional publishers.
Continue reading about Cool thing Thursday: Leanpub
Semantically similar articles hand-picked by GPT-4
- Different medium, different mindset
- Why you should never write a book in .doc
- Turns out I'll be writing a book
- The true difference between self publishing and using publishers
- It made me $500k but I think content is a bad business
Learned something new?
Read more Software Engineering Lessons from Production
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Software Engineering Lessons from Production
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️