
International number formatting without string tricks
Keep monetary units and large integers exact, preserve localized format parts, and test the difference between display, arithmetic and input parsing.
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.

Keep monetary units and large integers exact, preserve localized format parts, and test the difference between display, arithmetic and input parsing.

Inspect actual Argon2id records, measure three explicit policies and use a conditional migration write to preserve a password reset that committed first.

Calculate a tiny attention row, apply a causal mask, and follow the weighted value sum while keeping attention weights separate from an explanation.

Trace a shared scalar computation, reproduce its gradients, expose a detached branch and distinguish a ReLU kink from a gradient bug.

Track real byte values, dirty state, eviction and bypassed writes in four explicit cache policies, then compare complete-interval traffic.

Use vector scores, zero-error probabilities and a quadratic update to choose the next mathematics topic while keeping each inference within its assumptions.

A commute survey separates an observed zero, declined answer, not-applicable record, and collection failure. A worked analytical example with explicit assumptions and checked results.

Keep CLAUDE.md focused on verified repository facts, distinguish written instructions from remembered notes, and remove stale guidance before it misleads a task.

Trace separate chaining in a five-bucket phone book, distinguish a hash collision from a duplicate key, and explain the assumptions behind expected constant time.

Model order identity, reject orphan references, inspect cascades and separate database relationships from the policy for deleting a paid order.

Replace a three-bit field in an eight-bit word, verify unaffected bits, and see why device registers need a separate access contract.

Mark row and column headers in a plan comparison, preserve units and accessible names, and keep wide tables usable on narrow screens.