> For the complete documentation index, see [llms.txt](https://naz.gitbook.io/my-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://naz.gitbook.io/my-docs/get-started/index.md).

# Welcome

A growing collection of study notes on backend engineering and networking — built from lectures, courses, and real-world research.

## Why this exists

Most learning resources are either too shallow or too scattered. This site organizes technical content into structured, reviewable notes so you can actually retain what you study.

The notes follow a lesson-by-lesson order. Start with **Lesson 1** and work forward — each one builds on the last.

## Where to start

**Start here:** [Lesson 1: Understanding HTTP for Backend Engineers](/my-docs/backend-learning/understanding_http_for_backend_engineers.md) — the foundation for everything else on this site.

Once you're comfortable with HTTP fundamentals, move on to the networking notes to understand how data actually travels across the wire.

## What you'll learn

* **Backend fundamentals** — HTTP protocol, request/response cycles, headers, status codes, connections
* **Networking** — TCP/IP model, TCP vs UDP, how the web's protocols evolved from HTTP/1 to HTTP/3

## Lesson order

| Lesson | Topic                                    |
| ------ | ---------------------------------------- |
| 1      | Understanding HTTP for Backend Engineers |

Additional networking notes are available under Basic Networking — they're not part of the lesson sequence but provide useful context.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://naz.gitbook.io/my-docs/get-started/index.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.