The Engineer's Notebook

About

About the notebook

Notes from building backend and cloud systems, written to be used: open in a second tab while you work, not read once and forgotten.

What this is

Each note answers one practical need: a command you keep looking up, an order to learn a subject in, or a question that comes up in real work, answered with the reasoning left in. Every note also says what it is about twice, once in plain words and once in technical ones, so you can tell in a sentence whether it is the one you need.

Notes
50
Of reading
14 h
Tools covered
56
First note
9 Jun 2026

How it's organised

How a note is made

  • Each note is its own hand-built page, with its own layout, light and dark themes and diagrams, rather than text poured into a template.
  • Cheatsheets open with "Key terms in plain words": a glossary of the words the sheet uses, each linked from its first mention, with a preview on hover.
  • Diagrams draw themselves the first time they scroll into view, and can be replayed or paused. Readers who ask for less motion see them finished.
  • Everything has been used on a real project, and anything with a sharp edge says so next to it.

Who writes it

Shree Kumar Sharma

Shree Kumar Sharma

Cloud Backend Engineer

@shreesharma07Writing the next note

I am Shree Kumar Sharma, a cloud backend engineer in Gurugram, India. Distributed systems, Node.js and the cloud underneath them. The notebook is where I write down what I would have wanted to find the first time.

The full story, work history and projects are on the portfolio's About page.

Corrections and ideas

Found something wrong, out of date, or unclear? Want a note on a subject that is missing? Write to me.