What do you need to know in order to work in the web development industry?
Where should you start, in terms of really understanding the concepts now, and down the road?
What do all these weird-sounding terms mean??
In this podcast series, we’ll be pulling apart Kamran Ahmed’s Web Developer Roadmap to help you visualize and contextualize your self-education journey.
By the end of this series, listeners will understand the different subsets of web development, and what kinds of tools and resources you’ll need to learn in order to get a job. If you’re a new self-taught web developer, you’ll definitely want to tune in!
The Web Developer Roadmap by Kamran Ahmed (@kamranahmedse) provides a visual guide for navigating the complex world of web development. This week, we’re diving into the Back-End portion of the Roadmap.
And we’re going to pull apart the Roadmap, so I can help you (and actually, myself!) to better understand the problems that each of these topics solve.
In this episode, we’ll cover topics like:
- Understanding how the Back-End and Front-End interconnect
- Picking your first back-end language
- Building your first command line app
- Package Managers
- Standards & Best Practices (S&BP)
- Learning a Back-End framework
- Relational, non-relational (NoSQL), and graph databases
- RESTful APIs
- Authentication vs. Authorization (and their methodologies)
- Message brokers
- Search engines
- Web servers
- Graph databases
This is a REALLY packed episode! It’s even longer than the Front-End episode, and worth every moment of your time. You’ll probably listen to it multiple times, and I hope that you enjoy it more each time! 😊
Picking a Back-End Language
Containers (and Docker)
Preethi Kasireddy is a prominent explainer of all things complex, at levels I aspire to—so I definitely recommend anything by her! In this article, she goes into Containers, and gives some great context and explanation for why you need them.
NoSQL (Non-Relational) Databases
This video does an excellent job of explaining not only what they are, but why you’d want to use websockets.