Happy Halloween! We released a ton of new stuff on Boot.dev this October, and I’ve had a blast figuring out new mediums and tools we can use to create content. Anyhow, here’s to a great November glass clink. If you ever want to connect with me personally you can just reply here, I’d love to chat.
The short answer? On average, backend developers make either $82,462, $95,472, or $104,865 per year in base pay depending on who you ask. (I asked Glassdoor, Indeed, and Salary.com respectively.) StackOverflow uses medians instead, and their survey suggests the backend developers actually make upwards of $175,000 per year.
I’m really interested in the trends we see in the software engineering job market. Sometimes it’s really hard to tell a cohesive and accurate narrative about what’s happening because it just happens so dang fast, and very few people are collecting data on the matter.
During development you may sometimes notice you run a lot of commands to set up, build, test, and manage your project. Sometimes, these end up requiring several steps, or you have trouble remembering the exact command. One way to manage this is to set up aliases in your shell configuration. While this would work fine for yourself and for a single build system, it would not be possible to share it in a convenient manner.
Want to become a backend developer? Not surprising. Backend developers enjoy an average base salary of $160k per year, not to mention comprehensive benefits. And best of all? You no longer need a four-year degree to learn backend development. With the help of some of the best backend projects, you can prepare yourself for a backend development job in about nine months, even if you’re a total beginner.
Functions are one of the most versatile tools in any Python programmer’s toolbox. They enable code reuse and provide a form of abstraction. Python offers many different types of functions. In this article, I will be discussing the different types of functions you will encounter as a Python developer.
So you want to get into web development, and you keep hearing about “front-end” and “back-end” positions. The question is, which should you learn first? As someone who’s held both front-end and back-end positions, and even been a hiring manager, read on and I’ll give you my thoughts.
So you’re looking for the very best backend bootcamp of 2026. You’re not alone – most backend engineers earn over six figures according to Glassdoor, plus they have wide and varied job prospects. It’s a good gig.
It’s time for some speculation on my part I believe that the job duties of “back-end” and “DevOps” engineers will coalesce to include almost everything that “the user doesn’t see”. There will still be room for specialization, but these roles will become less distinguishable overall.
DevOps principles, and CI/CD specifically, are generally presented as a more efficient way to run a software development organization. While I hold the belief that CI/CD is more efficient and effective than manually testing and deploying code, I’d like to talk about something we don’t bring up quite as often.
The sexiest job title of the decade, data scientist, has spawned about a dozen equally sexy but somewhat confusing and overlapping job titles. The primary offshoot of a data scientist is a data engineer. Let’s talk about the difference between a data engineer and a back-end engineer, because frankly, the lines can get quite blurred.
I think we often do a great job of flogging the dead horse of whiteboarding problems when giving coding interview advice. Heck, that’s what I’ve dedicated the entirety of Boot.dev to. While the hard skills you’ll need to be able to solve technical interview problems are necessary, it’s also critically important to work on your soft skills.
I’m happy to announce that today we launched our new Learn SQL course! It was a ton of fun to write, but I also had a blast building the back-end infrastructure that allows students to write and execute SQL in the browser. If you’ve been wanting to gain a solid foundation of SQL skills, this course is for you!
Vim or VS Code? Tabs or spaces? Rails or Django? The world of programming is fraught with decisions to be made. Sometimes experienced developers are able to share their beliefs in a somewhat objective way. That said, we’re all human, and opinions can come across as gospel when we’re not careful.
“DevOps” is one of the most misunderstood terms in the software development industry. To be clear, I’m not the arbiter of truth when it comes to the definitions of words. That said, I’m here to say two things:
At work, computer scientists build and deploy programs, algorithms, and systems to solve real-world problems. In most tech jobs, they spend the majority of their time working in teams on new software products. Some computer scientists are more research-oriented however, and may spend time developing new algorithms or pushing the boundaries of what academia knows about certain CS questions.
I get really frustrated when I see people and companies online selling unrealistic dreams when it comes to coding education. It’s quite lucrative when you’re in the edtech industry to heavily exaggerate (or even lie) about how long it will take for learners to get job-ready. I teach backend development skills at Boot.dev and try my best to give students realistic goals they can reach for.
I recently spent far too long fighting with Vue’s keyup and keydown functionality while building Boot.dev’s front-end. I wanted to handle ctrl+period keyboard events and it took me forever to find the part of the documentation that addressed my use case. Hopefully, this guide can save you some time!
Mark your calendar, because we’re hosting another hackathon in the Boot.dev Discord server! The kickoff meeting will be on Thursday, September 1st at 4PM MST, you can RSVP for that event here in our Discord server. Everyone is welcome to participate, in fact, it’s free and we’ll have prizes for all the winners!
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.
In today’s modern, fast-paced world, we look to StackOverflow, Reddit, and hands-on courses to learn about computer science and software engineering. But there are some real benefits to using books as an additional resource.
Getting into computer science can be a daunting task. There are so many career paths down which a computer education can take you, so many programming languages to master, and so many skills to learn. I’ll give you a basic rundown of what computer science is, along with a plethora of resources and tools to help you carve out your own pathway into a computer science career.
In a word, the future of computer science is promising. In a few more words, the future of computer science is promising, but with challenges to overcome.
With so many job boards out there, it can be terribly confusing to know where to start when you’re looking for a programming job - especially if you’re looking for your first programming job. I’ve found that where you search for jobs is just as important as other key preparation steps you should take in your job search, like building a great resume and GitHub profile.
The future is bright for career options in computer science with remote work opening up doors that weren’t present before. Trying to navigate through computer science career options can be overwhelming what with all the options at your disposal. While we won’t go through every job option in the field today, we have a list of common yet crucial jobs to help you get started on finding the career that’s right for you. But first…