Back to learning
Node.js

Node.js: an API worth depending on

Design endpoints around resources, validate at the boundary, and fail in a way callers can act on.

  • Intermediate
  • About 3 weeks
  • 2 milestones
  • 3 steps
  • Every step reviewed
TypeScriptNode.jsNestJSREST API
Start this journey
What you will have builtAn HTTP API with honest status codes, validated input and errors that say what to do next.Start this journey

What this asks of you

Every figure below is read from the journey itself, not written about it.

IntermediateSome engineering experience assumed
About 3 weeksAn estimate, not a deadline
2 milestonesEach one claims a capability
3 stepsShort, and every one is built
Every step reviewedAn engineer reads all of it, when mentor guided

What you will be able to do

Every milestone claims one engineering capability. You reach it by building something, not by finishing a chapter.

ResourcesDesign an endpoint by naming the resource rather than the actionMost route arguments are really disagreements about what the resource is.
2 steps
Show the 2 steps
  • Name the resourcesReviewed

    Replace verb-shaped routes with resources and methods.

  • Choose your status codes deliberatelyReviewed

    Decide, per endpoint, what a caller learns from each failure.

BoundariesValidate untrusted input once, so everything behind it can assume it is safeDefensive checks scattered through a codebase are a sign the boundary is missing.
1 step
Show the step
  • Validate at the edgeReviewed

    Move every input check into the request boundary.

How the work is verified

  1. ReadThe context you need for this step, and why it matters. Never more than that.
  2. BuildYou produce something real. The work is yours, in your own repository.
  3. SubmitYou send it, with a note on what you chose and what you were unsure about.
  4. ReviewA senior engineer reads it and responds. They may ask for changes — that is the normal path through engineering review, not a failure.
  5. VerifiedThe capability is confirmed, it goes on your record, and the next step opens.

How you want to work

You choose when you start. Both cover the same journey and the same definition of done.

Mentor guidedReviewed by a person

A senior engineer is assigned to you. They read every submission, respond in writing, and decide when a capability is verified. Expect to be asked for changes.

Self pacedVerified by you

You work through the same journey and verify your own work against the same definition of done. Nothing is submitted to anyone, and nothing waits on anyone.

What you end up with

Counted from this journey, not described in general.

An HTTP API with honest status codes, validated input and errors that say what to do next.Built by you, in your own repository.
3 pieces of work, each read by an engineerEvery round and every comment stays on the record, including what changed between them.
2 verified capabilitiesEach one confirmed against its definition of done, with the name of whoever confirmed it. There is no certificate. The work is the credential.

Ready to start Node.js: an API worth depending on?

You will choose how you want to work on the next screen. Nothing starts until you confirm it. You can run several journeys at once, and each one is mentor-guided or self-paced on its own.

Start this journey