What I wish I logged earlier on every project

Most of my useful knowledge never made it into a README. It lived in Slack threads, commit messages, and “I’ll remember this” — which I did not.

This site exists so those notes have a permanent, public home.

What belongs in a build log

• Decisions — why we picked X over Y while the tradeoff was still fresh
• Incidents — what broke, how we found it, what fixed it
• Dead ends — approaches that failed so future-you does not retry them casually
• Env / infra gotchas — the stuff that never shows up in tutorials

What does not belong

Marketing copy. Feature announcements with no technical meat. Anything you would be embarrassed to paste into a teammate’s PR review.

A template I use

## Context
What we were trying to ship.

## What broke / what was unclear
Symptoms, logs, repro.

## Fix
Concrete change. Snippets when useful.

## Follow-ups
Tickets, monitoring, things still risky.

If the note takes more than twenty minutes to write, it is probably two notes.

I will keep replacing these seed posts with real write-ups. If you are a Pakistani developer figuring out freelancing, study-abroad logistics, or remote roles, there will be a separate tag for that later — same voice, different shelf.