Whose Clock?
Why a constant-rate sender doesn't need a phase-locked loop, where one is actually needed, the questions its equations leave open, and how to check an implementation that can't be exact.
Tag
Writing tagged “Essay”.
Why a constant-rate sender doesn't need a phase-locked loop, where one is actually needed, the questions its equations leave open, and how to check an implementation that can't be exact.
Why taking turns isn't enough to share a consumer fairly, how deficit round robin measures turns in work, and how a deliberately simple reference shows that an implementation follows the rules.
How agentic coding adds a boundary between the engineer and the program, and why working code must be simplified, described, and constrained.
Human limits, OpenBSD audits, privilege separation, and the operating-system boundaries that contain unseen defects.
Writing less code can make that code more secure.
The negative space of security: unintended behavior, explicit permissions, and what testing can—and cannot—establish.
Setting limits, questioning comments, and writing pure functions will simplify our code and save our brains for the most important work.
Making changes understandable, giving reviewers useful evidence, and making code review worth the interruption.