Earn an extra $50k+ per year by writing a programming book
without the headaches of self-publishing

If you've been programming a while, I’m sure you’ve read some sub-par programming books and thought, “I could write something way better than this.”

But you realize that once you finish the book, marketing is hard. It can take a long time to write an entire book and you want it to generate income when you’re done.

You might think:

“I could write with a traditional publisher. The prestige would be nice. But why write with a big publisher for 5% when I could self-publish and keep all of the money?

Because building an audience is hard. To acquire an audience of 150,000 people, will take 1-2 years, if at all.

To make your book really succeed, you need a strategy, email marketing, content marketing, web-design, editing, customer support, and a thousand other details.

You start to realize that the cost of doing it alone is just too high and you don’t want another failed side project.

With our team and process we’ll help you write and market a book that will be loved by thousands of programmers (and sell) for years.

We have:

  • A process for writing books - so you’ll never be stuck with writer’s block
  • An audience of over 150k developers to sell to once you’re done
  • Highest royalties in the business

We’ll train you in the lifelong skill of clearly articulating your thoughts and we’ll help you sell.

The result will be a book people want -- and will buy -- earning you reputation and revenue for years.


What is Fullstack?

Support to write and sell your programming book

Fullstack provides training, editing, marketing, and sales support for authors to write a technical book.

Authors also receive mentorship, not only in technical and prose editing, but also how to how to sell. You already know how to program, but now you can teach others and earn money at the same time.


We’ll teach you how to write a book and how to sell it


We’ll introduce you to our audience and tell them about the book

Operational Support

We’ll help you with editing, marketing, customer support, email campaigns, and everything you need to turn a manuscript into a finished product.


Why Work with Us?

No writers block

We have a clear, step-by-step process for writing high-quality, project-based programming books.

Built-in audience

Programmers love our books which is why we have an active audience of over 100,000 readers. This means when your book is ready, there are people who want to buy it.

Training on how to sell

Unlike other publishers that simply assign you to an editor that corrects your grammar, we’ll teach you how to sell products online.

Highest royalties in the business

We split royalties with our authors 50/50.


How it Works

At a high level, here's is how the process will work:

  1. 📐 We’ll meet and plan a list of topics to cover, based on data & research (1 week)
  2. ⚗️ We’ll distill our research into a specific outline (1 week)
  3. 🔁 We’ll iteratively write the chapters in a code → draft → revision loop (roughly 2 weeks per chapter)
  4. 👩‍🎓 After the book is about 50% finished, we’ll invite a group of beta readers who will give us feedback on what works, and what needs changed.
  5. 📯 As it gets closer to launch, we’ll collaborate to prepare marketing tools such as a email campaigns, a sales website, and blog posts
  6. 🚀 We launch!
  7. 👨‍🏫 After launch, we’ll continue to collaborate on blog posts and marketing the book -
  8. 💰 ... and you’ll receive a check every month.

You’ll be assigned a Producer who will give you guidance on every step of the process. You’ll meet with them every week.

We also have supplementary training videos, templates, and materials for book creation. You can use these materials to accelerate the creation process while keeping the quality high.

The process from outline to launch will take between 12-16 weeks.

The result? You’ll spend 3-5 months creating a book people will love and an asset that will generate returns for years.


What's Different about Fullstack?

Project-based Tutorials

Some books share out-of-context tips or isolated code snippets, with no guidance on how to integrate that code into a real app.

All of the code in our books is runnable. Meaning, we provide the full code for every example - so if the reader is ever lost they can open up the code, make changes, explore it, and run it for themselves.

Show how the pieces fit together

Similarly, many API documentation writers draw a small circle of responsibility around what they'll teach. There are often industry conventions and implied context that beginning students simply don't know.

In our Fullstack books, we teach the reader all of the necessary context. Not only "core APIs" but also:

  • recommendations for popular packages and how to use them
  • practical tips for debugging and how to learn how to deal with errors
  • tactical advice on how to structure project files and patterns for data architecture
  • and provide real-world, industry-known context

The result is not only that the student knows the core library, but rather they come away with a toolset for improving their career.

It's more than a book - it's an income-bearing asset

Writing with Fullstack is more than putting together a manuscript and walking away, blindly hoping it sells.

Together, we'll be collaborating to craft and market the book beyond what would happen with a "traditional" publisher.

For example, in addition to the book we'll collaborate to create:

  • blog posts
  • educational email campaigns (to folks who ask for them)
  • supplementary "teaser" material (e.g. 30 Days of React)
  • bonus video content

It's more work than throwing a manuscript over a wall. But investing more time in marketing (combined with higher royalties) results in reputation, skill growth, and financial gains commensurate with the extra effort.


Request for Books

Below is a list of topics we’re actively looking to write about.

Click here for a real-time list of Request for Books (including those already in progress).

You don’t have to pick from this list to apply to write a book with us. Programming ecosystems change quickly and we love writing about new tech.

That said, we’re looking for authors to write about the following topics:

  • Web Development

    • Angular
    • React
    • Django
    • Flask
    • Elm
    • ReasonML
    • GraphQL
    • Prisma
    • .NET
    • Phoenix
  • Web Servers

    • Python
    • Golang
    • Node.js
    • Elixir
  • Mobile Development

    • Flutter
    • Dart
    • Kotlin
  • DevOps

    • Docker
    • Kubernetes
    • Serverless
  • Cryptocurrency

    • Ethereum
    • Building trading bots
    • Smart Contracts
    • Solidity
    • Cryptography
  • Desktop

    • Electron
  • Machine Learning & AI

    • Pytorch
    • Machine Learning Algorithms
    • Deep Learning
    • Reinforcement Learning
  • Data Science

    • R
    • Python
    • D3
    • Hadoop
    • Spark
  • Functional Programming

    • Elm
    • ReasonML
    • OCaml
    • Haskell

The Fullstack Series

The primary books we’re looking to write are the Fullstack series. The differentiating factor of Fullstack books is that they go beyond the core APIs and teach how to build real apps using the ecosystem tools.

For example, Fullstack React starts by teaching "React Core", but quickly branches out into all of the real-world topics you need to build React apps such as routing, GraphQL, form handling, data architecture with Redux, and so on.

Fullstack Node.js will cover not only core functionality such as async IO, but also writing servers with express, writing CLI tools, talking to databases, file organization, testing, and deployment.

Fullstack Kubernetes: The Complete Guide to real-world container orchestration might walk through how to deploy a simple app, but also how to scale instances, industry patterns for isolating failures, advice on how to manage secrets, how to use helm to manage packages (and write your own), etc.

The key idea is runnable code and instruction that shows the fastest way to build real projects and take you from beginner to intermediate.


Meet the Team

Nate Murray

Nate is the co-founder of \newline. He is the co-author of several programming books and courses including Fullstack React, ng-book, Fullstack Vue, and the \newline cryptocurrency series.

Nate formerly was an early engineer at IFTTT and worked in applied research at AT&T Interactive in distributed computing and data science.

Sophia Shoemaker

Sophia is a full stack developer and the founder of Shop Sifter and editor the Fullstack React Newsletter.

She's a mentor at Hackbright Academy and is excited to encourage and empower women looking to get involved in programming. When she isn't cobbling code, she can be found flying in her husband's Beechcraft Bonanza and playing with her 2 kids.


What Our Authors Say

Hassan Djirdeh

Fullstack Vue

“Writing Fullstack Vue was my first foray into writing a published book and I genuinely enjoyed the experience working with the Fullstack team.

In addition to royalties being a lot more than expected (which is always great :)), everything we did was collaborative and engaging: from first draft, to writing and finally publishing.

I'm already considering producing my next project with Fullstack!"

Devin Abbott

Fullstack React Native

"The Fullstack team has a clear formula for creating great books that readers love. We started by figuring out what topics we wanted to cover. Then we wrote a brief outline of each chapter before diving in. Each chapter revolves around a different project, so it's easy to split up the work between multiple authors while still keeping a consistent style throughout the book.

When we were ready to release the first version, the Fullstack team took care of selling the book, sending out promotional emails, and converting relevant customer support tickets into Github issues. Overall, the process was pretty easy, and I was able to focus mainly on writing. Working with Houssein, Anthony, and Sophia was a lot of fun, and I would absolutely do it again!"

Anthony Accomazzo

Fullstack React

"Writing and launching my first ever title was a thrill - and I have Fullstack to thank. Their support was instrumental in both getting the project off the ground and ensuring it reached the hands of thousands of readers.

The additional income stream I established has been key to bootstrapping my other entrepreneurial endeavors. They're a wonderful and talented team!"

Amelia Wattenberger

Fullstack D3

I didn't mean to write a book. I filled out the Fullstack writer survey mostly out of curiosity — would other developers be interested in learning about data visualization? After that, I met with Nate to talk about topics, then we solidified an outline, then I had written a whole chapter! Nate's process is so smooth, at no point did I feel like I was actually "writing a book".

Honestly, I would never have been able to write a book without the team — the accountability is great, but I also would have thrown in the towel at any number of obstacles that popped up: the writing & typesetting process, updating code easily, not to mention the overwhelming idea of marketing the book.

Writing Fullstack D3 was a thoroughly enjoyable, fun process that really solidified my understanding of the topic. The writing was over before I knew it, and we've sold way more copies than I expected! Plus, the compliments from my peers have been really amazing.

I would definitely recommend that you at least fill out the survey — who knows, you could have a finished book in a few months!


Should I Apply?

We’re particular about who we choose to work with, but possibly not in the ways you would expect.

You don't need to:

  • have thousands of Twitter followers
  • have written a book before
  • have perfect English
  • take a sabbatical from your job
  • be the famous inventor of a popular open-source project

You do need:

  • A desire to teach others
  • The patience to slow down and explain in detail the steps required
  • The ability to recognize and articulate patterns that experts know but beginners don’t
  • The ambition to build a “passive” income stream
  • Availability in your schedule of 5-10 hours per week for the next 12 weeks

We’ve listed topics we’re interested in writing about above in Request for Books. However, don’t feel limited by that list. Programming ecosystems change quickly and we love writing about new tech.

If this sounds like you then apply by filling out the form below.



To apply to write a book, click here


How long does this book have to be?

It depends on what we're trying to accomplish. Generally our books are between 8-10 chapters. There's no strict page or word count -- we'll use however many words it takes to communicate the idea.

Fullstack React is a beast, weighing in at over 800 pages. However, it also had 6 authors.

Fullstack Vue was about 400 pages, written by a single author.

Even 400 pages might sound like a lot, but by the time you add code and images, you'll be surprised at how fast it goes.

Does it take a lot of time?

Generally our books are between 8-10 chapters. It typically takes 1-2 weeks to research, outline, code, and write a good chapter -- assuming you have 5-10 hours per week to work on it.

Typically a book can be finished in 3-5 months.

How much money can I make?

This really depends on the book topic, the marketable-audience size, and the time spent on blog posts after launch. (It also depends on how many co-authors you have.)

To give you a rough idea, I (Nate) have written about some of the economics publicly here on Hacker News.

Every book is different and there are no guarantees, but for a sense of scale, as of writing (Q3 2018), all of our authors make thousands per year, several make tens of thousands. More than one has made greater than fifty thousand for multiple years. But again, it depends.

How long will the book sell for?

It depends! All other things being equal, it's better to try and write in a way (and about a topic) that won't age too quickly.

We've found that our programming books tend to sell longer than even we'd expect. We released ng-book 2 in 2015 and, while we have made several updates, the book continues to be a best-seller.

Should I have a co-author? How many?

You should probably have one, but it isn't a requirement.

We've worked with solo authors on Fullstack Vue, Zero to Deep Learning, and Modern AngularJS.

The process also works well with two authors.

However, if you have too many co-authors (e.g. more than 2) then there's a risk no individual author feels a deep ownership over the work and the project can drag on.

So our recommendation is: if you have a close friend, who you trust, who wants to work together - then let's do it! Otherwise a single author works.

What other books have you published?
What topics can I write about?

See our Request for Books section above.

Can I do a video course instead?