Another three months, another royalty statement from Packt. Three months post facto. Of course.
My effective hourly rate for Data Visualization with d3.js is now €5.1/hour. Up from the €3 it was last time.
And that's the beauty of writing books.
After the initial blood and sweat and tears, I don't have to do anything. As long as it keeps selling, money keeps hitting my bank account. Were I to do some active promotion and build a newsletter or some manner of business around the books, sales would be even better.
Similar to what's happening with my other book - Why programmers work at night. I keep poking at it and doing minor things here and there when I have time, and it keeps selling. It's still not finished, but it makes just enough sales a month to cover my Uber expenses.
Which begs the question, why the hell am I still busting my arse freelancing?
Well the money's infinitely better, that's true. And I don't make enough from books to cover anything even close to my living expenses.
But book revenue is additive. Freelancing revenue is linear.
You see, no matter how much better I get at programming and getting clients, my revenue can only scale linearly. It's bound by time and no matter how high my daily or weekly rate can go, there is only so much time. And I'm hitting a ceiling with my rate. And when I break this ceiling, a new one will be waiting just around the corner.
With books ... writing four to five a year would give me hockey stick growth.
The d3.js book took me 332 hours. With a full-time writing schedule I can fit 6 of those into a year with no days off. With weekends and such I could easily write 5 technical books a year.
On topics I don't even know yet. It's a magnificent way to learn, writing a book. That's how the d3.js book happened. I had no clue about d3.js beforehand.
But what about money?
Well in its first quarter the book made €1019 of royalties. Second quarter, €676. Assuming a logarithmic fall towards a minimum, next quarter is going to be around 500, then 400 and so on.
Eventually sales will reach an asymptotic limit and I'm going to get some €100 a quarter. Or €400 a year. By then it will have made me some €5000 or €6000, spread over some two years.
Were I to write five books with similar sales every year I'd be making some €30,000 a year. Just enough to live like a normal person in Slovenia, or barely scrape by in a swanky place like San Francisco.
This is where the hockey stick comes in. Because book revenue never falls to total zero, my yearly income would grow. Slowly at first, but by the time I was 50 I could live comfortably having done nothing but writing from now until then.
If I started writing full-time right now, I could be making a living off writing in just two or three years. Maybe this is my next in the 11 lives you get?
After 17 years I'm getting kind of tired of programming anyway ... anyone want to invest 90k in me becoming a full-time author?
Here's how it works 👇
And get thoughtful letters 💌 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
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
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️