In my first year of writing technical content for software engineers, I reached hundreds of thousands of readers around the world, met some of my role models, and made more money than I would have working a student job on campus. I wrote this book to help you use writing to achieve your goals.
Earn money, make connections, and get noticed.
The rates I earn from writing tutorials, usually $250 to $500 per article, add up. That isn't the only reason to write. A portfolio of published writing could help you earn a raise, land a new job, or reach new clients or customers for your business.
Practice a proven writing method.
There is no substitute for time spent writing. With intentional practice, you will become better at writing. What you practice, and how you do so, determines the rate of improvement.
Level up your skills, wherever you use them.
While this book focuses on teaching you how to envision, create, and publish mid-length technical tutorials and articles, the principles and practices developed will help you write anything from a short README to an entire technical book.
Features interviews with:
- Courtland Allen: Indie Hackers
- Jeff Atwood: Coding Horror, Stack Overflow, Discourse
- Chris on Code: scotch.io
- Peter Cooper: Cooper Press
- Angel Guarisma: Former Director of Content at Linode
- Matt Levine: Money Stuff at Bloomberg
- Mark McGranaghan: Go by Example
- Patrick McKenzie: @patio11, Kalzumeus
- Tracy Osborn: Hello Web Books
- Daniel Vassallo: The Good Parts of AWS
- Cassidy Williams: Former Speaker with React Training
Writing and publishing are incredibly rewarding, with tangible and intangible benefits. I write to increase my skills, earn an audience, teach what I know, and, yes, make money. Regardless of why you write, this guide aims to provide you with the techniques you will need to reach your goals.
If you have read similar books on writing in other fields, for example, a recent copy of Writer's Market, many of the ideas in this book will seem surprising, or even wrong. This book is designed to teach you how to write complete, accurate, and compelling technical articles and tutorials, and how to sell your work to clients. This market, thanks to its adjacency to software engineering, is substantially different from markets for short fiction, essays, recipes, journalism, or even informational articles on topics like personal finance or marketing.
This guide is composed of three acts. First, we will walk through the entire process of writing an article, from pitch to content, editing to publication. Next, we will explore the process in action with three full sample articles. Finally, we will discuss the business of writing and how to turn your newfound confidence in the article- writing process into a profitable side gig or even full-time employment. Along the way, we will hear from successful members of the software/writing community about their best practices. These excerpts are lightly edited for readability. Full transcripts of each interview are available in Appendix A, and I encourage you to read all eleven complete interviews as they are loaded with valuable insights.
(No Email, Signup, or CC required)
Free Sample Chapter: https://philipkiely.com/assets/files/wfsd_chapter1_sample.pdf
Free Sample Chapter (Audiobook): https://youtu.be/glTuJ2kniGg
Is this book good for beginning writers?
Yes. Writing for Software Developers takes you through my process, one step at a time, and helps you create and publish your first article.
Is this book good for experienced writers?
Yes. If you have already written and published technical content, you will enjoy the nuances of the eleven expert interviews and extract key insights from the main text.
How much programming experience do you need to read this book?
Some, but not as much as you might think. I started writing technical content as a junior in college, less than two years after I started programming. Many of the code examples I used in articles were based on projects that I had worked on much earlier in my journey toward becoming a software engineer.
What formats are available?
Your purchase of Writing for Software Developers includes a PDF, EPUB, and MOBI of the ebook as well as an audiobook narrated by Griffin Mareske in MP3. The audiobook is 6 hours and 35 minutes long and does not include the appendices, images, or code snippets.
Can I share this book with my team?
If you purchase a single copy, please respect the license terms and do not distribute any copies. If you want to share the book with your team, company, or class, please purchase a team license. Academic and nonprofit organizations can contact me for fifty percent off a team license.
Is there a return policy?
I have a 30-day no-questions-asked refund policy. If you don't like it, let me know and I will refund your money.
For more, see https://philipkiely.com/wfsd or check out my appearance on Software Engineering Radio: https://www.se-radio.net/2020/09/episode-426-philip-kiely-on-writing-for-software-developers/
You've purchased this product
See it in your libraryView in Library
We charged your card and sent you a receipt
You'll need an account to access this in our app. Please create a password to continue.
Download from the App Store or text yourself a link to the app
Thanks for purchasing a copy of Writing for Software Developers! I put a ton of work into researching and writing this book and I hope it delivers the actionable insights that you are looking for.
If you find the book helpful, it would mean the world to me if you left a five-star review on Gumroad, Goodreads, or Twitter. If it didn't live up to your expectations, remember that I offer a 30-day money-back guarantee, just send me an email and I'll refund your purchase. If you have any questions or concerns, or you just want to tell me how awesome the book is, you can always reach me by email at email@example.com.
Good news! Since you already have a Gumroad account, it's also been added to your library.