ClaroCal · Engineering
Engineering notes
Occasional notes from building ClaroCal: the trade-offs behind the product, written up honestly. Latency, budgets, architecture, and the decisions we would defend in a code review.
These are working notes, not announcements. Each one covers a real decision from the codebase, the options we prototyped, and what we would tell a friend who was about to make the same call.
Latest · 003
Interface latency · UX honesty
The chip that refuses to guess
Our quick-add box shows how long a task will take before you press Add. The number comes from a server the browser has never met. This is the story of the 250 milliseconds in between, the four designs we prototyped, and why a late answer beats a fast wrong one.
live · quick-add
Typing “brush teeth tomorrow”…
All notes
003
The chip that refuses to guess
Debounce, latency, and the psychology of showing a number you can actually stand behind.
002
The bundle ceiling
Hard perf budgets in CI, a ratchet that tightens them, and the decisions they made for us.
001
One Durable Object per user
A personal server per user that wakes on alarms and hibernates, and the CI test that keeps it asleep.