Idempotency in Node.js workers: how to avoid charging a user twice
A backend pattern for making Node.js jobs safe to retry, with examples for payment jobs, idempotency keys, Redis claims, and stored state.
Featured guide
Build a developer portfolio recruiters understand
A simple developer portfolio structure with examples for showing projects, decisions, results, code quality, and contact information clearly.
Read the guide
Editor's picks
View engineering guidesDesigning a fraud detection event pipeline in Node.js
A practical Node.js fraud event pipeline with stable event contracts, idempotent consumers, rules, risk scores, review queues, audit logs, and replay safety.
tsconfig.json explained: the TypeScript options that actually matter
A plain-English guide to the tsconfig options that affect real projects: target, module, moduleResolution, strict, lib, include, and noEmit.
Will AI coding tools make junior developers less valuable?
A practical look at junior developer value in the age of AI coding tools, with skills that still matter.
Guided reading
View all paths01
Build reliable backend workflows
5 guides02Structure, retries, failed jobs, recovery, and fraud-event processing.
Secure an API at its boundaries
7 guides03Authorization, abuse controls, webhooks, browser policy, and deployment identity.
Understand TypeScript and its runtime boundary
4 guides04Compiler configuration, strictness, npm failures, and HTTP behavior.
Turn backend work into portfolio proof
4 guidesProject scope, decision writing, hiring signals, and interview preparation.
New guides
Recently publishedBackend Architecture
GitHub OAuth token rotation: how to migrate without logging everyone out
A practical GitHub OAuth token rotation guide: handle expiring access and refresh tokens, rotate safely, preserve sessions, and recover when users return with old credentials.
Node.js and TypeScript
Node.js 26.8.1 upgrade checklist: what to test before moving a backend
A practical Node.js 26.8.1 upgrade checklist for backend teams, covering runtime compatibility, native dependencies, tests, observability, and rollback planning.
Developer Security
GitHub code scanning's Mitigated reason: when a vulnerability is not fixed
Use GitHub code scanning's Mitigated dismissal reason honestly when external controls reduce risk, while preserving remediation ownership and review evidence.
Developer Security
MCP allowlists in GitHub Copilot: a practical least-privilege setup
Use GitHub Copilot MCP allowlists to control remote and local servers, fail closed on bad settings, and review tool access before enterprise rollout.
Developer Security
GitHub Code Quality Actions path changed: update reports and cost tracking
Update GitHub Actions reports for the dedicated Code Quality workflow path and actor without losing code-scanning history, billing data, or audit visibility.
Developer Security
GitHub OAuth apps with multiple redirect URIs: secure migration guide
Configure GitHub OAuth apps with multiple callback URLs safely, preserve state validation, prevent redirect confusion, and migrate tokens without breaking users.
Developer Security
CodeQL 2.26.3 for JavaScript and GitHub Actions: what teams must retest
Review CodeQL 2.26.3 changes for JavaScript, TypeScript, Vue and GitHub Actions, including a breaking custom-query removal and updated taint models.