
Split a cache address into tag, index and offset
Derive a sixteen-bit cache address split, trace conflicting reads, check line-spanning byte intervals and recalculate tag storage and associativity.
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.

Derive a sixteen-bit cache address split, trace conflicting reads, check line-spanning byte intervals and recalculate tag storage and associativity.

Build an explicit token budget for an international document assistant, reserve output capacity, and handle oversized inputs without silently dropping evidence.

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.

Compare selection-time and arrival-time TTLs, test exact expiration boundaries, and carry response age through an explicit HTTP caching example.

Place 0x12345678 at four byte addresses, reconstruct it explicitly, and keep byte order separate from width, alignment and signedness.

Trace a policy question through retrieval, context assembly, citations, and abstention to build a RAG pipeline whose evidence can be inspected.

Keep Gregorian birthdays separate from instants, build a localized native-date comparison and test why consecutive noons can be 23 or 25 hours apart.

Trace a mobile draft across background transitions, process loss and delayed save callbacks, with a clear boundary between UI state and committed content.

Define what one analytical row represents, keep receipt and line measures separate, and distinguish a missing line from an observed zero with executable SQL.

Build a bracket checker that reports the first mismatched character, keeps opening positions on a stack, and states where a real parser needs more context.

Map the responsibilities of an export feature across interface, API, worker, storage and operations before dividing the work.