Chapter 1 — What Is Backend Development?

The why

L0 told you what the backend talks to. L1 is the backend itself — the daily work, the tools, the rhythm. By chapter 11 of this level you'll have shipped a real API. Right now, get the lay of the land.

What backend engineers do (the actual list)

1. Design APIs — figure out the endpoints, shapes, status codes.
2. Implement business logic — the rules of the product (pricing, permissions, workflows).
3. Talk to databases — read, write, optimize queries.
4. Wire third-party services — Stripe, email, S3, OpenAI.
5. Handle errors and edge cases — half the job is "what if this fails?"
6. Write tests — unit, integration, sometimes E2E.
7. Review code — usually 1–3 PRs a day.
8. Deploy and monitor — push to prod, watch dashboards, fix what breaks.
9. Be on-call — sometimes.
10. Talk to PM/design/frontend — alignment costs more than typing.

If you imagined backend devs as silent coders typing in a black void, sorry — half the job is communication.

The top 6 backend stacks

We'll use Node + Express in this course because:

• It's the most common starting stack for new web companies.
• JavaScript is the only language that runs both client and server.
• The ecosystem is huge and shippable in a weekend.

Every concept transfers. If you understand backend with Node, you can rewrite it in Go in two weeks.

"Works" vs "good" code

Code that works:

app.get('/users', async (req, res) => {
  const users = await db.query('SELECT * FROM users');
  res.json(users);
});

Code that's good:

app.get('/users', requireAuth, async (req, res, next) => {
  try {
    const limit = Math.min(Number(req.query.limit) 

The second one:

• Checks auth — requireAuth.
• Validates input — clamps limit.
• Respects authorization — listVisibleTo(req.user, ...) decides what they can see.
• Handles errors — try/catch + next(err).
• Doesn't leak — uses a service instead of inlining SQL.

The first works in a demo. The second survives production.

Three frameworks: Express, NestJS, Fastify

Worth knowing the lay of the land — even though we'll use Express:

• Express — minimal, unopinionated, the lingua franca. The most flexible choice and the easiest to learn. We're using it.
• NestJS — opinionated, structured, TypeScript-first. Looks like Angular for the backend. Great for big teams.
• Fastify — like Express but faster, with built-in schema validation. Worth knowing for perf-critical APIs.

Each maps to the others 1:1 in concept. Learn one cold, the others are weekend projects.

Where backend ends and DevOps begins

Modern backend devs do some DevOps. There's no clean line. Typical split:

At a 20-person startup: you do both. At a 5,000-person company: you specialize. Both are valid careers.

L6 of this course covers the DevOps side every backend dev needs.

Career arc

A rough trajectory:

• Junior (yr 0–2). Build features. Fix bugs. Learn the stack and conventions.
• Mid (yr 2–5). Own services. Mentor. Make architectural choices.
• Senior (yr 5+). Set direction. Design new systems. Reduce risk.
• Staff / Principal. Cross-team. Reduce ambiguity. Pick which 5 things matter out of 50.

Most "backend salary" growth comes from moving from feature work to system design — which is exactly the L4–L7 path of this course.

Common mistakes (early in career)

Is backend right for you?

You'll probably love backend if you:

• Like puzzle-solving more than visual design.
• Enjoy reading docs and specs.
• Get satisfaction from "this is 10x faster now."
• Don't mind invisible work — most backend wins are invisible.

You might prefer frontend if you:

• Care a lot about the look and feel.
• Like instant visual feedback.
• Enjoy UI animation, motion, design.

There's also fullstack — knowing both ends. Most modern jobs blend them.

Exercises

1. Beginner. Pick a SaaS you use. List 5 backend operations it must do.
2. Beginner. Skim the docs of Express, NestJS, and Fastify. Note which one feels closer to your taste.
3. Intermediate. Find a real GitHub issue tagged good first issue in a backend project. Read the discussion.
4. Advanced. Read a postmortem from a real outage (status.github.com, AWS Status, Stripe Postmortems). Identify which layer broke.

Interview questions

Beginner. Why did you pick backend? (There's no wrong answer — but have one.)

Senior. Describe a system you built. What were the trade-offs? This question will define every interview from year 2 onward. Practice telling the story.

Summary

Backend developers design APIs, run business logic, talk to databases and external services, handle failures, write tests, and ship. Node + Express is one of the most common starting stacks, but the concepts transfer. "Good" code does more than "work" — it checks auth, validates input, handles errors, and stays testable.

Quick recall

• Backend = APIs + business logic + database + integrations + reliability.
• Top stacks: Node, Python, Go, Java, Ruby, C#.
• "Works" ≠ "good."
• Career grows by moving from features to systems.

Quiz

1. Name three things "good" backend code does that "works" code might skip.
2. Why does this course use Node + Express?
3. List two ways backend ends and DevOps begins.
4. What's the difference between a junior, mid, and senior engineer?