Last week there was a lull in exams - that I now almost regret indulging - and as often happens ideas started flowing. Plenty of ideas for new products, productifying old prototypes and so on.
An idea I'd had a few weeks ago came back to me, what if I was to write a book? It seems I can get a few people to read my blogposts, would they read a book?
On Thursday I set out to test the book idea. With more readers than all the other posts on this blog combined, Why programmers work at night was the perfect candidate for a topic.
After re-reading that essay thing, I realized it's full of assumptions supported by anecdotal evidence from a group of one, arm-chair-science reasoning about causes and atrocious writing.
I can totally do better!
By evening the pitch was written, basic goals outlined and a landing page set up on leanpub. -> https://leanpub.com/nightowls
Writing the book I want to talk to as many programmers of all types as possible, conduct short interviews with them to be featured in the book, conduct a survey or two and once and for all answer three important questions:
- _D_o programmers work at night?
- Does this happen more than in other creative disciplines?
- How the hell do you handle a night-time programmer in your life?
The experiment was simple, if I can get 100 people to sign up by the end of September I was going to write the book.
So far 238 have signed up. Most within the first 48 hours of the page being up. Hooray \o/
Right, now I have this book to write ... it's a bit scary, very exciting and I think I can pull it off. But we won't know for certain until I do.
Here's the plan:
- In October I start conducting interviews - send me an email at firstname.lastname@example.org if you want to help
- By November I want to publish the first minimum viable book, a beta version if you will
- By December the book should be in a final state and publishable "for real"
- Continue updating the text as new ideas/info surfaces and publish an updated version every couple of months
To make things more interesting, I'm writing the book out in the open on github -> https://github.com/Swizec/nightowls. There I will be accepting bug reports, anything you feel is wrong, just tell me.
Oh and you get to see the content before it's published, but pdf's are nicer to read than markdown files ;)
- It's a Dirty Job... (Guest Post by Kasia James)
- How to teach a journalist programming
- Use Simple Words
- How Many Books Should I Write At Once?
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 ❤️