By Developers, For Developers
We know. It feels a little bureaucratic. But after 20 years of doing this, we feel this is the best way to start a conversation.
The template for submitting a proposal is shown below. Please download your own copy, fill it in, and send it to proposals@pragprog.com.
Thanks!
We’re glad you are here! Thanks for considering The Pragmatic Programmers as your publishing partner.
What happens next? Start by getting to know our books and our style. We focus on readers and keep things hands-on. We skip background and theory, and instead start with simple activities that build confidence fast. Read through some of our books, and then use this document to tell us about your idea. You can download free sample chapters from each book’s table of contents at PragProg.com.
Once we receive your proposal, we review it as a team. Sometimes we can give an immediate yes. A definite no usually just means we’re not the right publisher for the project. Most of the time, this document becomes the starting point for a conversation where we dig in and learn more about what you have in mind.
We know there are a lot of unknowns at this stage, and some of these questions might be tough to answer. That’s okay. This isn’t a test. Just give us your best thinking and we’ll take it from there.
Please note that we want to hear your voice and see your writing. While we know LLMs are now part of many writers’ toolkits, we ask that you compose both this proposal and the sample chapter without AI assistance.
Finally, please delete the writing prompts after you’ve answered them.
<!- fill this in –>
For each author: please tell us a little about yourself:
<!- fill this in –>
Tell us about your experience and relation to the topic, including: * Your relationship to the community (how active you are) * Public speaking about this topic (podcasts, talks, classes taught) * Other content you’ve written on the topic (articles, books, tutorials) * Ways readers can connect with or follow you: - Twitter handle - LinkedIn address - Blog - Github page
<!- fill this in –>
<!- fill this in –>
When you think of the final book, how thick will it be (inches, mm, words, or rough page count)? Most of our books run 20-25 pages per chapter.
<!- fill this in –>
<!- fill this in –>
Our books are not just a bunch of facts. Instead we want them to take the reader on a journey where they will come to master some particular topic. So tell us, in one or two paragraphs each:
<!- fill this in –>
<!- fill this in –>
<!- fill this in –>
This might be the trickiest section. We’re not asking you to commit to a table of contents, but we do want you to think about the structure and the reader’s journey. Every author will start with some kind of plan, and every author will find that that plan changes as they start writing (and as our editors get involved). So what’s yours? Just give us a list of major headings and a sentence describing each. There’ll probably be from 8 to twelve sections here. You don’t need to include things like the preface and bibliography.
<!- fill this in –>
We’d love to see a sample chapter from somewhere in the middle of the proposed book as a separate attachment. We are looking for hands-on, actionable content on a fairly meaty topic.
If you’ve written any other books, please link to them here.
<!- fill this in –>