Write on the Boot.dev Blog

We’ve just opened up the Boot.dev Blog to public contributions! We’re really excited to see all the great stories that our readers and students will create.

Why should I write on Boot.dev?

By writing and publishing your ideas publicly, you can:

Impress future employers
Help you solidify what you’ve recently learned
Help others find answers that took you a long time to research
Gain traffic and domain authority for your own blogs and projects
Get helpful feedback on your writing skills from our editorial team

The reason to write on Boot.dev is the same reason you might write on FreeCodeCamp or HackerNoon: To get your writings out to a wider audience, and to get high-domain authority traffic and links back to your own projects or blog.

What kinds of articles can I write?

Boot.dev is a platform for anyone interested in learning to code, particularly backend development in Python, JavaScript, and Go. As far as the stories we’ll publish, we accept well-written articles that are at least somewhat related to programming.

How do I submit articles?

First, know that it’s free to contribute articles to Boot.dev, and we do not pay you for your contribution. No money changes hands.

Second, know that you are allowed to drop tasteful dofollow links back to your own projects and sites. Take advantage of our great domain authority and reach! As long as your content is original and well-written we’re happy to expose your writing to our readers.

Read the full contributing guide here on how to submit your story.

Keep in mind: Your article must be original to Boot.dev.

We don’t want to spam our readers with content that they’ve already seen elsewhere. Your article must be original to Boot.dev. That said, after your original piece is published on Boot.dev, you can republish it elsewhere only if you set the canonical link back to the Boot.dev article.

Using GitHub Issues to Hack Together A Feedback System

Jul 31, 2022 by Lane Wagner - Boot.dev co-founder and backend engineer

Boot.dev has been my side-project for the last couple of years now. Being a learning path for backend developers focused on quality over quantity, I knew early on that it needed to have a really tight feedback loop from students. We had (and still have) a Discord server where myself and the students hang out, and that worked okay at first. Unfortunately, Discord channels have a couple problems when it comes to issue tracking:

How Not to Ask for Help Online

May 20, 2022 by Lane Wagner - Boot.dev co-founder and backend engineer

I’ve spent an unhealthy amount of time online over the course of my life, and in the last couple years I’ve been managing a Discord server for people who are learning computer science. Like all online communities, we have ban, kick, and moderation policies so that we’re not overrun with spammers and other non-contributors. However, I’m not perfect, and I have realized recently that we get a decent number of members who at first glance seemed like a spammer, but it turns out they just have no idea how to communicate online in a way that’s useful to themselves and others.

Top 10 Communities For Learning to Code

Apr 20, 2022 by Zulie Rane - Data analysis and computer science techincal author

Why you need a coding community The one thing that every programmer has in common, whether they’ve only ever implemented a “Hello World” program or they’re considered a “senior” software engineer, is the need to continuously learn. New technologies, programming languages, frameworks, libraries, and conventions are constantly being introduced to the industry. As a beginner, it can be hard to suss out what you need to know to enter the profession, and once you’re a proficient coder, it’s tiring to constantly investigate trending topics in tech.

An Overview of Boot.dev's Full-Stack Architecture

Jan 10, 2022 by Lane Wagner - Boot.dev co-founder and backend engineer

Because I’ve had several inquiries on this topic, I thought it would be interesting to publish some information on how the boot.dev website and platform work, and how I’ve organized all the technologies I’m using. I’ll do my best to keep this list updated in the future as I migrate from older tools and technologies to newer ones, but assume that this might be a bit out of date by the time you read it.