Topic · ENGINEERING

Writing on engineering for PMs

Vibe coding, agent-assisted development, schema-first thinking, and the engineering surface a senior PM should own.

4 posts in this topic. See all writing.

May 2026ENGINEERING7 min
Caching is a hospitality problem.
The cache is a boarding-house register, not a hash map. The bua of a four-room mess in Sutrapur explains who she lets stay, who she evicts before noon, and why LRU is a landlady's instinct that the Netflix caching team eventually wrote down on a slide.
May 2026ENGINEERING8 min
Bun is the new Node and that's fine.
A team switching JavaScript runtimes is usually less dramatic than the standup that decided to do it. The interesting part of moving from Node to Bun isn't the runtime, it's that the audit forces you to confront which of your dependencies were quietly lying about being standard the whole time.
May 2026ENGINEERING8 min
The build is the brief.
Compile errors and broken tests are the most honest user research you will ever get from a feature. The PRD only tells you what the team wishes were true, the build only ships what is actually true, and the fastest way to close the gap is to let the build read the spec back to you.
May 2026ENGINEERING8 min
Agentic products need contract tests, not unit tests.
A unit test on a deterministic function asks for an exact byte. An agent answers in a different shape every Tuesday, and the byte changes. What you actually want is a contract on what the answer must look like, witnessed by three named clauses, the way a kabin-nama gets signed in a Wari sitting room.