Editorial policy

What gets published

• Engineering notes from real projects: backend architecture, distributed systems, infra, and AI engineering.
• Cheatsheets and technical terms intended to be practical while building.
• Postmortem-style “what went wrong” writeups when the lesson is transferable.

Accuracy & sourcing

• Claims are intended to match what is visible in the article (code, benchmarks, diagrams, or linked references).
• When a post references external facts (e.g. documentation, RFCs), links are provided where reasonable.
• Examples are tested when feasible, and revised if behavior changes across versions.

Updates & corrections

If something is wrong or outdated, I prefer fixing it quickly and noting the change. See the corrections policy for how updates are tracked.

Disclosures

• If a post includes affiliate links or sponsorships in the future, it will be clearly labeled on the page.
• Product mentions are not endorsements unless explicitly stated.

Contact

If you want to report an issue or suggest an improvement, use the contact page.