
Move permission checks out of the interface
Learn backend authorization with an organization wiki, scoped roles, direct endpoint tests and checks for alternate data paths.
The journal / Ideas in progress
Engineering & everyday learningSoftware, systems, and the things I’m learning along the way. From first principles to AI in production.
Find something to readA little theory. A lot of practice.

Learn backend authorization with an organization wiki, scoped roles, direct endpoint tests and checks for alternate data paths.

Use RFC 9457 Problem Details for stable API errors, with field-level validation data, safe diagnostics and client behavior that survives wording changes.

Compute a tenant-scoped email key, test concurrent uniqueness and compare retired-key reservation with an active-only index and its restoration conflict.

Build a first backend vertical slice around one note-creation request, durable storage, clear input rules and a recovery case.

Separate omitted properties, explicit null and empty strings in a JSON update contract, then validate each state without accidental truthiness defaults.

Protect concurrent profile edits with a version-checked SQL update, distinguish zero rows from errors, and test conflict resolution and unversioned writers.

Transfer credits with PostgreSQL, check affected rows, observe commit from two sessions, and reproduce rollback, insufficient funds and repeated-request limits.

Validate runtime JSON with NestJS DTO classes and ValidationPipe, choosing explicit coercion and unknown-field behavior instead of trusting TypeScript types.

Trace changing inventory reads in PostgreSQL Read Committed, compare Repeatable Read, and locate snapshot boundaries at the first query and statement start.

Ask precise backend review questions about identity, partial updates and external effects, even while learning the codebase.

Protect tenant-scoped membership identity, preserve roles during repeated adds, and reproduce an insert-or-fetch query that returns nothing after a conflict.

Choose HTTP methods for an order API by their defined effects, then document replacement, retries and deletion with concrete requests.