Right now I'm writing two books at once and yes that was a terrible idea. Please avoid doing this if you at all can.
Self-publishing -> November 2012 to March 2013 (5 months) -> 104 hours worked. Includes researching, writing, marketing, everything. About 40 pages written.
Publisher -> late January 2013 to March 2013 (1.5 months) -> 101 hours worked. Just researching and writing. About 100 pages written.
Might be the tight chapter deadlines I keep missing, might be the nice project coordinator lady asking me what the fuck do I think I'm doing via email every couple of weeks.
But them's the facts. I get more writing done when working with a publisher.
- Author Development: Residual Income Through Book Publishing
- 10 Proofreading Tips For Self-Publishers
- If A Publisher Offers You a Contract for Your Self-Published Book, Will You Be Forced (By Amazon) To Refund Past Customers Who Bought It?
- Writer, Undercover: Four Submission Tips
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 👇
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
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 ❤️